-
-
Notifications
You must be signed in to change notification settings - Fork 248
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
Add the "{..}" construct to syntax lookup #652
Comments
That is an Example: @val external someObj: {..} = "someObj"
someObj["name"] = "Patrick"
someObj["twitter"] = "@ryyppy" |
Mmm, so like an object map, kind of a { [ key: string]: any } in typescript? Shouldn't then this be on the syntax lookup? Edit: I mean, these quirks are really difficult to search. I am partly not using rescript because of that (also I don't believe I'm the target audience). |
There's a few more subtle things to consider when using this type. (had to create a new issue to clarify some things here). It should be on the syntax lookup and most likely in the object / interop sections at some point. |
If it helps. This is used very rarely, it has legitimate uses, but is generally an escape hatch. The |
Hi @ryyppy and @CarlOlson, <input
onChange={evt => {
let x = ReactEvent.Form.target(evt)["value"] // x is 'a
setIntegerValue(_ => x) // x is int, should not happen!
}}
/> I agree with @alarbada, this looks like something that shouldn't even take place in a language like Rescript. @ryyppy I think in my example the compiler should panic if there's no decoder in place because |
I have no idea what that actually does, I found it in some declaration files.
The text was updated successfully, but these errors were encountered: