Skip to content

Resubmit "[Parse] Implementation for SE-200 (raw strings)" #19170

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

Merged
merged 1 commit into from
Sep 6, 2018
Merged

Resubmit "[Parse] Implementation for SE-200 (raw strings)" #19170

merged 1 commit into from
Sep 6, 2018

Conversation

johnno1962
Copy link
Contributor

Reverts #19168 to reinstate #17668 which missed a “squash” first time around.

Implementation for SE-200

@johnno1962 johnno1962 changed the title Revert "Revert "[Parse] Implementation for SE-200 (raw strings)"" Resubmit "[Parse] Implementation for SE-200 (raw strings)" Sep 6, 2018
@beccadax
Copy link
Contributor

beccadax commented Sep 6, 2018

@johnno1962 Could you amend a nicer commit message into this? In two years, nobody will care that this commit reverts a revert.

Edit: Actually, I'll just change it when I squash it. Nevermind.

@beccadax
Copy link
Contributor

beccadax commented Sep 6, 2018

@swift-ci please smoke test

@beccadax beccadax merged commit 4da8cbe into swiftlang:master Sep 6, 2018
@johnno1962
Copy link
Contributor Author

🥂Thanks @brentdax for all your help on this proposal.

@johnno1962 johnno1962 deleted the revert-19168-revert-17668-master branch September 6, 2018 22:35
@benlangmuir
Copy link
Contributor

This seems to have broken the ASan bots because of accessing memory out of bounds https://bugs.swift.org/browse/SR-8724. I'm going to revert in #19214. The code in the lexer that's looking at -2 and -1 offsets into a string looks responsible.

@benlangmuir
Copy link
Contributor

Nevermind, looks like @rintaro already has a fix ready in #19206.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants