-
Notifications
You must be signed in to change notification settings - Fork 38
[10.1] Redefined async functions don't support named arguments #707
Comments
So this is clearly an error: let _ = (~a=1, 1) but this (after desugaring) let _ = @res.async (~a=1, 1) could be handled differently |
I don't have move access 🤔 or did you want me to close and re-log? |
Let me do it. |
Example of redefined
|
Here: #708 |
Thank you! I'll test it as soon as I can. |
I'm migrating my codebase to 10.1 and I have functions called
async
(someexternal
, somelet
) that were defined long before ReScript considered adding async/await.Is this supposed to be allowed now that
async
is a keyword? Simple functions work, but functions with named arguments throw a syntax error after the function call such asDid you forget a => here?
when I attempt to call them:I'm happy to say redefining
async
shouldn't be allowed, but thenlet async
andexternal async
should trigger an error rather than at the call site.The text was updated successfully, but these errors were encountered: