Skip to content
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: also handle literal types when computing upper bound #1103

Merged
merged 1 commit into from
Apr 25, 2024

Conversation

lars-reimann
Copy link
Member

Related to #1081

Summary of Changes

Also update the type computer to handle literal types as upper bounds of type parameters.

Copy link

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ REPOSITORY git_diff yes no 0.12s
✅ TYPESCRIPT eslint 2 0 0 4.41s
✅ TYPESCRIPT prettier 2 0 0 1.1s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by OX Security

Copy link

codecov bot commented Apr 25, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (c14159b) to head (ffd36b9).

Additional details and impacted files
@@            Coverage Diff            @@
##              main     #1103   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          106       106           
  Lines        20799     20801    +2     
  Branches      4090      4091    +1     
=========================================
+ Hits         20799     20801    +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@lars-reimann lars-reimann marked this pull request as ready for review April 25, 2024 10:41
@lars-reimann lars-reimann merged commit 3f1ab6f into main Apr 25, 2024
7 checks passed
@lars-reimann lars-reimann deleted the fix-upper-bound-computer branch April 25, 2024 10:41
lars-reimann pushed a commit that referenced this pull request May 2, 2024
## [0.14.0](v0.13.0...v0.14.0) (2024-05-02)

### Features

* `this` expression ([#1111](#1111)) ([c7bd0fa](c7bd0fa)), closes [#1107](#1107) [#1110](#1110)
* allow literal types as upper bounds of type parameters ([#1102](#1102)) ([c14159b](c14159b)), closes [#1081](#1081)
* Check truthiness of value ([#1131](#1131)) ([0b059a1](0b059a1))
* check usages of `@PythonName` and `@PythonCall` on overriding methods ([#1100](#1100)) ([3021166](3021166))
* partial code generation for multiple targets ([#1114](#1114)) ([5461a1b](5461a1b)), closes [#1079](#1079)
* Stubs for `safe-ds` version 0.22.1 ([#1130](#1130)) ([6f7100d](6f7100d))
* various methods to work with strings ([#1112](#1112)) ([b6d4f16](b6d4f16)), closes [#1108](#1108)
* visibility modifiers for any module member ([#1104](#1104)) ([3d43d38](3d43d38)), closes [#1083](#1083)

### Bug Fixes

* also handle literal types when computing upper bound ([#1103](#1103)) ([3f1ab6f](3f1ab6f)), closes [#1081](#1081)
@lars-reimann
Copy link
Member Author

🎉 This PR is included in version 0.14.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@lars-reimann lars-reimann added the released Included in a release label May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
released Included in a release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant