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
I don't think there is something we can do about this one because we can't garante that there is no self variable available in the runtime.
I suppose we could argue that const self = self will always fails in JavaScript because of Uncaught SyntaxError: Identifier 'self' has already been declared.
And that let self = self can sometimes works in JavaScript, if self is available globally before.
For me this issue, ask Fable to do more than verifying F# and lean toward JavaScript/TypeScript compiler/runtimes responsibility.
Description
Creating a top-level binding to a
Global
value with the same name causes a reference errorRepro code
https://fable.io/repl/#?code=PYBwpgdgBAYghgIwDZgHQGFgCcwChcAuAnuFAKIAeI2BAzlALy5QtQDaAPAOJLAJxIAfAF1mrWgTgEAlgGMoAWzAKEYLFFpgkAMwBcUPgCtGUCFOkA3MAHkISImJYTz8pSrVQK+6RAImAjPgofpo6JpTUWHSoodq4wVAA+rHhVDS0MVraQA&html=Q&css=Q
Expected and actual results
Ideally, this situation would either be a compiler error or create an shadowed aliased value. In local scopes, a similar reference is aliased locally:
For public toplevel fields, which are automatically exported, I'm not sure how it should behave.
Related information
4.22.0
The text was updated successfully, but these errors were encountered: