fix(allocator): prevent putting drop types into arena#6626
Conversation
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @overlookmotel and the rest of your teammates on |
Your org has enabled the Graphite merge queue for merging into mainAdd the label “0-merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix. You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link. |
CodSpeed Performance ReportMerging #6626 will not alter performanceComparing Summary
|
8ddc979 to
3e8b3ed
Compare
f5e8578 to
9c2ed7b
Compare
3e8b3ed to
45bdb68
Compare
9c2ed7b to
240ea95
Compare

Should not be merged.
Is a quick and dirty check that we do not put any drop types into either
oxc_allocator::Boxoroxc_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
Droptypes intoBoxorVec. So this demonstrates that #6623 does not introduce any memory leaks. Good!However, as the docs say, we cannot rely on
needs_dropnot producing false positives, so this could start producing erroneous compilation errors in a future version of Rust.