-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Assertion error in latest master #1305
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
* constant was renamed * let was introduced * classifier supports additional options again
@derekcicerone thanks for reporting this. Can you share the sources that cause this error to occur? |
This issue happens on a medium-sized proprietary code base (over 20k lines) that I can't share in its entirety unfortunately. I was hoping that the stack trace would be sufficient but if not I can try to jump into the code with a debugger to figure out what might be going wrong. |
I see the issue, i just do not see how it happened. a complete stack would be helpful as well. |
Hmm yeah, part of the weirdness of this issue is that the stack trace seems to begin at the hasVisibleDeclarations call. I just updated to the latest code in master and this is the "full" stack trace I see:
|
This is paused in the debugger just before the exception is thrown. |
error message looks similar to #1288 with minimal repro case: // Debug.assert when generating declaration file
var x: <T>() => T; checking visibility for var x: {<T>(): T}; |
Good call, that looks like the same issue. Closing this one. |
I just updated eclipse-typescript to the latest code on master and got this error when attempting to get diagnostics:
Partial stack trace:
The text was updated successfully, but these errors were encountered: