-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: potential stack overflow when computing types of lambda parameters #1173
Conversation
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports |
7e62aae
to
af619cd
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1173 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 110 110
Lines 19238 19227 -11
Branches 4114 4119 +5
=========================================
- Hits 19238 19227 -11 ☔ View full report in Codecov by Sentry. |
## [0.16.0](v0.15.0...v0.16.0) (2024-05-16) ### Features * eda plot view ([#1161](#1161)) ([a216743](a216743)), closes [#955](#955) [#986](#986) * integrate version 0.25.0 of the `safe-ds` Python library ([#1174](#1174)) ([f357c38](f357c38)) * prefix keywords with `^` to treat them as identifiers ([#1172](#1172)) ([90bd47c](90bd47c)) ### Bug Fixes * potential stack overflow when computing types of lambda parameters ([#1173](#1173)) ([d89511e](d89511e))
🎉 This PR is included in version 0.16.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Summary of Changes
Due to the interaction between the type computer and the scope provider, the previous approach to prevent endless recursion when computing the type of lambda parameters could fail. This PR provides a more robust implementation to fix this issue.