fix(allocator): prevent putting drop types into arena #6626
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.
Should not be merged.
Is a quick and dirty check that we do not put any drop types into either
oxc_allocator::Box
oroxc_allocator::Vec
.Unfortunately, this is probably not reliable enough to use. From
needs_drop
's docs:So the fact that tests and conformance pass on this PR does prove that no code path that they exercise attempts to put
Drop
types intoBox
orVec
. So this demonstrates that #6623 does not introduce any memory leaks. Good!However, as the docs say, we cannot rely on
needs_drop
not producing false positives, so this could start producing erroneous compilation errors in a future version of Rust.