Remove DerefMut impl for JS::MutableHandle
#574
Merged
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.
Like with #572 and #573 this impl allows for improper aliasing with the GC. With this type it also allows for outright use after frees, since
JS::MutableHandle
, like a raw pointer, has no lifetime attached to it. Eventually that's a justification for removing theDeref
impl as well, but once thing at a time.There's only one use of this in servo, which is removed in the accompanying PR: servo/servo#36161
Like with #572 and #573 I added an unsafe
as_mut
method, though it is unused locally this time as well as in servo. It feels like a reasonable escape hatch to share even if it isn't currently used.Part of #569, and can be merged entirely independently from #572 and #573.