-
Notifications
You must be signed in to change notification settings - Fork 12.4k
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
Fixed braceless type tags with types starting with an open parenthesis #57167
Conversation
Looks like you're introducing a change to the public API surface area. If this includes breaking changes, please document them on our wiki's API Breaking Changes page. Also, please make sure @DanielRosenwasser and @RyanCavanaugh are aware of the changes, just as a heads up. |
@typescript-bot test top200 |
Heya @sandersn, I've started to run the parallelized Definitely Typed test suite on this PR at 1f4862e. You can monitor the build here. Update: The results are in! |
Heya @sandersn, I've started to run the diff-based top-repos suite on this PR at 1f4862e. You can monitor the build here. Update: The results are in! |
Heya @sandersn, I've started to run the diff-based user code test suite on this PR at 1f4862e. You can monitor the build here. Update: The results are in! |
@jakebailey do you remember if jsdoc parsing shows up in perf results anymore? Having a lot of tokens was a significant cause of slowdown in JS comment parsing when I profiled. So I don't want to add tokens unless it's for a good reason. Is there a lot of un-braced usage of types? It's only supported in TS for compatibility, since the braces are supposed to be required. |
@sandersn Here are the results of running the user test suite comparing There were infrastructure failures potentially unrelated to your change:
Otherwise... Something interesting changed - please have a look. Details
|
Hey @sandersn, the results of running the DT tests are ready. |
@sandersn Here are the results of running the top-repos suite comparing Everything looks good! |
@typescript-bot perf test this faster |
Heya @jakebailey, I've started to run the faster perf test suite on this PR at 1f4862e. You can monitor the build here. Update: The results are in! |
No, not really. |
@jakebailey Here they are:
tscComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
Developer Information: |
Right. But since they are optional in this context I'd expect this to work (there is an explicit boolean set here that allows it). I don't want this for myself - I'm not using JSDoc types anyway. It's just a problem I noticed when working on #57110 and such a braceless type came there (in the original issue) from the real-world code. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not convinced that this is very valuable, but it does fix an inconsistency, and it shouldn't hurt the fast path for scanning jsdoc comment text.
Can you update this PR from main before I merge? There has been a lot of churn in baselines recently. |
@sandersn done |
fixes #57166