Use unsafe slicing #106
Closed
Use unsafe slicing #106
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bjorn3
suggested changes
Apr 19, 2019
| @@ -148,7 +148,7 @@ impl<'p> ParserStream<'p> { | |||
| } | |||
|
|
|||
| pub fn get_slice(&self, start: usize, end: usize) -> &'p str { | |||
| str::from_utf8(&self.source[start..end]).expect("Slicing the source failed") | |||
| unsafe { str::from_utf8_unchecked(&self.source[start..end]) } | |||
There was a problem hiding this comment.
This function should be unsafe. The start or end might not be at the start or end of a character, which makes the str invalid.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Solves #82