-
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
Error on replacement character only in top-level scanning #58227
Conversation
@typescript-bot test it |
@jakebailey Here are the results of running the user tests comparing Everything looks good! |
@jakebailey Here they are:
tscComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
Developer Information: |
@typescript-bot perf test this |
@jakebailey Here they are:
tscComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
tsserverComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
startupComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
Developer Information: |
@jakebailey Here are the results of running the top 400 repos comparing Everything looks good! |
@typescript-bot run dt |
Hey @jakebailey, the results of running the DT tests are ready. Everything looks the same! |
Thanks Jake! |
This one came to me in the shower; everyone with this character "legally" in their files can only have put them into string literals or comments. If we just check this at the top level scan function, we'll never have a false positive because it'd definitely be a parse error at runtime. If any of the other scanner functions (e.g.
scanIdentifier
) see this character code, they're going to bail out anyway because it's an unexpected character, then this new case will hit.I could also modify this to check only at the start of a file, but since we're now back in the switch-case where we process all of the other scanning, this isn't actually inefficient anymore.
Fixes #57930