Repository navigation
Keep the references to a lambda parameter's generics in struct fields and inner pairs - #447
Merged
Rigidity merged 1 commit intoNov 19, 2026
Conversation
… and inner pairs A field of a struct whose type is an untyped lambda parameter's keeps the references to the callee's generics that are in it, the way an element of a pair does, and so does an element with them deeper inside, such as `p.first` for `p: ((A, Int), Int)`. The field is reached through the pairs the struct's type is made of before it's substituted, and is the same type as the substituted one, so only the inference of the call's generics sees the difference.
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
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.
Part of #362 (step 13e, layer 8 of 9).
13e.4 (#441) wraps the callee's generics in an untyped lambda parameter's type as references, so that a bound on the lambda's return type reaches them. A field access kept the reference only when the element was the reference itself. Now
wrapped_atkeeps the element as it was before substitution in two cases:first/rest, whenever a reference is anywhere in the element, through pairs, unions and structs;The kept type is the same type as the substituted one, so only the call's generic inference sees the difference. Newly compiled cases:
let r: (5, Int) = nested_map(fn(p) => p.first, 5)withp: ((A, Int), Int), andp.first.first;wrapper.valueandlast.valuewithWrapper<A>andLast<A>parameters;p.firstwithp: (Wrapper<A>, Int)andp: ((A, Int) | nil, Int).A field that doesn't reference the generic, such as
wrapper.other: Int, isn't narrowed, and that's pinned.Left as is (provisional): references aren't kept through aliases (
firstof aList<A>) or unions of struct copies.The stack (#362 step 13e, layers 6–9)
These layers close the gaps that the merged 13e layers (#438–#442) left, so the generics campaign ends with no follow-ups. Each layer is its own PR:
6. An argument's expected type counts when it's what the call's solution has to be:
wrap(map(fn(x) => x, 5))with(5, Int)expected.7. List items past the end of the expected pairs:
first(([2], [3, make()])).8. Struct fields and inner pairs keep a lambda parameter's generic references.
9. A lambda's shared or caller generics are instantiated when its body captures none of their values: the soundness limits that 13e pinned.
Fuzzer, per layer.
infer-fuzz --compareagainst baselines from main6aea07a5, on all four configurations (generators 1 and 2, seeds0..4000and4000..8000). Every layer has 0 regressions and 0 unsound variants, changes no variant that main infers, and leaks no{generic N}. Newly inferred variants, cumulative: 37 (6), 40 (7), 40 (8), 143 (9). The top PR has the full table.Breaking changes. None. No program that compiles on main changes its type, CLVM output or diagnostics. Pinned errors that now compile get the type that explicit instantiation gives, and each is a test.
Review. Three rounds:
Any; it's limited to a real list end now.T(x as T), so a value escaped with the wrong type. It's fixed, and pinned innames_the_callers_generic.one_of_two_lambdas_captures.Mutant rule. Every mutant ran in a scratch worktree, under
timeout 120, after a separate build step.Note
Medium Risk
This changes which types are inferred for calls with lambda arguments, list literals and field accesses, all in the compiler's call inference. A mistake would reject valid programs or accept unsound ones. The risk is limited by these points:
Changes by area:
call_inference.rs: the hint rule for an argument's expected type; which lambda parameters are instantiated (generic_parameter_types,names_restored_generics); instantiation in the alternative solve.lambda.rs:LambdaParameterandLambdaBody::captures_generics.list.rs: items past the end of the expected pairs.field.rs:wrapped_atandkeeps_reference.compiler.rs:ArgumentFrame::lambda_parametersholdsLambdaParameters.rue-hir/database.rs:next_hir_id,hirs_betweenandsymbol_count.tests/types/generic_inference_*: new tests and moved pins.