-
-
Notifications
You must be signed in to change notification settings - Fork 908
Instantiate generics in mutually recursive functions before unification #5071
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
Open
abs0luty
wants to merge
2
commits into
gleam-lang:main
Choose a base branch
from
abs0luty:fix-type-inference
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
9af0a58 to
7dde5f7
Compare
96d4132 to
980e01e
Compare
...r__tests__action__type_variables_in_let_bindings_are_considered_when_adding_annotations.snap
Outdated
Show resolved
Hide resolved
821799f to
1049608
Compare
0761e59 to
d1a7ec5
Compare
d1a7ec5 to
7356784
Compare
7356784 to
8c375f3
Compare
8c375f3 to
1e806ed
Compare
…ns before unification
```gleam
pub type Test(a) { Test(a) }
pub fn it(value: Test(a)) { it2(value) }
pub fn it2(value: Test(a)) -> Test(a) { it(value) }
pub fn main() { it(Test(1)) }
```
Before this change the compiler compared generic "sketches" directly to inferred types
in mutually recursive calls, causing false mismatches when generics behaved rigidly.
After the patch the compiler instantiates generics (based on annotations or inferred
concrete types) and updates the environment so mutually recursive functions unify correctly.
This resolves spurious type-errors in recursive scenarios.
1e806ed to
62de43d
Compare
```
fn wibble(a, b, c) {
↑
let x: a = todo
fn(a: b, b: c) -> d {
todo
}
}
```
After action:
```diff
- fn wibble(a: e, b: f, c: g) -> fn(b, c) -> h
+ fn wibble(a: e, b: f, c: g) -> fn(b, c) -> d
^ original name is preserved
```
When the "add annotations" code-action is used, the compiler now retains the
original type-variable names from the user's annotation instead of replacing them
with fresh or default names.
This ensures that added annotations reflect the user's naming exactly and prevents
confusing or misleading variable renaming.
62de43d to
c05b965
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR closes: