Propagate expected dict value type into dict literal typing#8359
Open
Propagate expected dict value type into dict literal typing#8359
Conversation
rescript
@rescript/darwin-arm64
@rescript/darwin-x64
@rescript/linux-arm64
@rescript/linux-x64
@rescript/runtime
@rescript/win32-x64
commit: |
cristianoc
approved these changes
Apr 18, 2026
Collaborator
cristianoc
left a comment
There was a problem hiding this comment.
Legit.
I guess a first class support for dict would avoid the issue, but might be more invasive.
(And async etc).
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.
Currently, this fails:
It fails because
dict{}expression is emitted asPrimitive_dict.make(["health", {get: 200}]), and that makes it loose type info. This PR propagates the expected dict type info further, which means the above code will work.As a nice side effect, this PR also improves type error messages for dict. This:
Will currently fail on the whole
dict{}(although it's just1.that's wrong). After this fix it'll fail on1.instead (Expected JSON.t, got float).@cristianoc can you think of a better cleaner way to do this?
Also, Codex is saying these cases are also broken and could be fixed the same way:
These fail today: