Repository navigation
Give the Rust lambda route a parameter type it already knew #9182
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
Closed
Closed
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
24be7f5
Stop transcribing a benchmark into a .dag authority, and declare the …
734aa40
Give the Rust lambda route a parameter type it already knew
4fd38a5
Regenerate the stage0 mirror so the lambda change is no longer inert
01086fa
Name the two unavailable-lambda-param policies instead of passing a Bool
b099261
Merge main into the lambda-param route branch
dc4e4b7
Regenerate the seven drifted stage0 mirror files so the .dag authorit…
57994a5
Map binds the element of its carrier, and the ? carrier was omitted f…
91ecabc
Merge main into session/deep-ant-102-transcribed-benchmark
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When the optional value is itself parameterized, such as
List<Int>?,normedbecomes the requiredList<Int>, butis_single_childremains true and the following branch extracts and returnsInt. Consequently, an optionalmaplambda is inferred as receivingInteven though Rust'sOption::mapsupplies the wholeList<Int>, causing incorrect body resolution or lambda annotations. Gate child extraction on!carrier_is_optional, or returnnormedimmediately after removing optionality.Useful? React with 👍 / 👎.