Ryan Cavanaugh
Ryan Cavanaugh
`erasableSyntaxOnly` is very explicitly *not* a moving-target flag that corresponds to exactly whatever syntax some version of nodejs currently supports. It is about banning syntax that can't be correctly handled...
What was the declaration emit in 5.5?
What's the observable manifestation of this difference? `SymbolLinks` is internal.
A union type can't have 1 member, so you're not going to see the union flag there. Your code must be able to handle this case.
A symbol has a `declarations` list that you can check the forms of. A runnable sample code would be a lot easier to work with/demonstrate than prose; I'm not sure...
The problem is that this is apparently circular; it implies the existence of `$$$$$bar`. In cases where this isn't circular, it's already possible: ```ts type PrefixedWith$ = T & {...
> I think this is unexpected behavior, and that this shouldn't cause an error. I can't think of a type argument that can be passed to Test2 that doesn't satisfy...
How does the compiler know what the output of `Exclude` is going to be, and that it's *definitely* going to have `"b"` in it? It's not correct to just evaluate...
> I think something should be implemented to make circular references behave more predictably to save developers from wasting time. "more predictable" here generally means "error *more*", we already want...
We have a separate issue tracking better interactivity with tooltips, which might subsume any use cases here