You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It will work as soon as I land the change to eliminate fuzzy arrows... :)
Changing the return type is a red herring - making a nested function changes it from a function typed variable (fuzzy arrow type) which can be re-assigned, to a concrete function which cannot be re-assigned (non-fuzzy arrow).
/cc @leafpetersen
Take the following code:
This should work:
f
has typedynamic -> void
, or as the inference currently infers:dynamic -> Null
.However I get the following error message:
I can remove this error message in two ways:
dynamic
toObject
(which should be the same thing).Null
tovoid
(by making it a nested function).Neither should be necessary.
The text was updated successfully, but these errors were encountered: