Skip to content

Compute word boundary flags in start state. #308

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
Dec 29, 2016

Conversation

BurntSushi
Copy link
Member

At some point, I think I had convinced myself that we didn't need to
compute word boundary flags for the initial state, but it turns out that
we do.

Fixes #271

At some point, I think I had convinced myself that we didn't need to
compute word boundary flags for the initial state, but it turns out that
we do.

Fixes rust-lang#271
@BurntSushi BurntSushi self-assigned this Dec 29, 2016
@BurntSushi
Copy link
Member Author

@bors r+

@bors
Copy link
Contributor

bors commented Dec 29, 2016

📌 Commit 8d764ea has been approved by BurntSushi

@bors
Copy link
Contributor

bors commented Dec 29, 2016

⌛ Testing commit 8d764ea with merge e2f0850...

bors added a commit that referenced this pull request Dec 29, 2016
Compute word boundary flags in start state.

At some point, I think I had convinced myself that we didn't need to
compute word boundary flags for the initial state, but it turns out that
we do.

Fixes #271
@bors
Copy link
Contributor

bors commented Dec 29, 2016

☀️ Test successful - status-appveyor, status-travis
Approved by: BurntSushi
Pushing e2f0850 to master...

@bors bors merged commit 8d764ea into rust-lang:master Dec 29, 2016
@BurntSushi BurntSushi deleted the fix-271 branch December 29, 2016 05:48
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.

2 participants