Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign up[breaking change] Make raw pointer fields private #110
Conversation
This is necessary for safety; otherwise safe Rust code could cause memory-safety violations by writing to the `raw` field and then calling safe methods.
mbrubeck
changed the title
|
@bors-servo r+ |
|
|
bors-servo
added a commit
that referenced
this pull request
May 17, 2018
[breaking change] Make raw pointer fields private This is necessary for safety; otherwise safe Rust code could cause memory-safety violations by writing to the `raw` field and then calling safe methods. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/rust-harfbuzz/110) <!-- Reviewable:end -->
|
|
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.
mbrubeck commentedMay 17, 2018
•
edited by larsbergstrom
This is necessary for safety; otherwise safe Rust code could cause memory-safety violations by writing to the
rawfield and then calling safe methods.This change is