-
-
Notifications
You must be signed in to change notification settings - Fork 610
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
fix Issue 22825 - #line parsing doesn't follow the spec #13727
Conversation
|
Thanks for your pull request, @ibuclaw! Bugzilla references
Testing this PR locallyIf you don't have a local development environment setup, you can use Digger to test this PR: dub run digger -- build "master + dmd#13727" |
| this.tokenizeNewlines++; | ||
| scan(t); | ||
| this.tokenizeNewlines--; |
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.
Bikeshed topic, whether to just make this field a bool parameter of scan() or not. I'm on the fence either way.
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 think this problem will take care of itself if you implement the changes requested in #13728
#13728 only takes care of |
|
Having read your comments, I see what you mean though, we'll wait and see after (or if) the other PR has been accepted though. |
|
In the meantime, added a spec PR here dlang/dlang.org#3234 |
|
@ibuclaw needs rebase! |
|
Tests moved to #13728. |
1 similar comment
|
Tests moved to #13728. |
Because these special token sequences are sensitive to newlines, they should not be allowed after the introducing
#token.