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
A major point of conflict between TS/Flow and the ES spec is with generic type instantiation:
letfoo=newFoo<T>(1)
That production is parsed by TS and Flow to be a single constructor call, but it's also valid ES, equivalent to the following:
((newFoo)<T)>1
IMHO, breaking the below code is a non-issue as I very highly doubt anyone is relying on that behavior (and it's easy for browsers to collect usage metrics on, too), but it's still worth mentioning as a potential risk. It also will tremendously complicate any grammar specification for it, requiring probably multiple cover grammars.
The text was updated successfully, but these errors were encountered:
A major point of conflict between TS/Flow and the ES spec is with generic type instantiation:
That production is parsed by TS and Flow to be a single constructor call, but it's also valid ES, equivalent to the following:
IMHO, breaking the below code is a non-issue as I very highly doubt anyone is relying on that behavior (and it's easy for browsers to collect usage metrics on, too), but it's still worth mentioning as a potential risk. It also will tremendously complicate any grammar specification for it, requiring probably multiple cover grammars.
The text was updated successfully, but these errors were encountered: