Move low-memory faulting to FutureFeatures.md #433
Merged
Conversation
This file contains 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
|
lgtm |
1 similar comment
|
lgtm |
jfbastien
added a commit
that referenced
this pull request
Oct 28, 2015
Move low-memory faulting to FutureFeatures.md
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.
There was general consensus in #204 and again in recent discussions to have low-memory faulting be a post-MVP future feature since it fits in well with the other fine-grained memory control features. This PR moves mention of low-memory faulting from AstSemantics.md (which is the MVP) to FutureFeatures.md and expands on the option mentioned in #204 of treating low-memory separate from
mprotect(since it allows more efficient impl when hw memory protection isn't available).