refactor(allocator): fix unsafe_op_in_unsafe_fn clippy warnings

[overlookmotel]

Continuation of #21210.

[overlookmotel]

• docs(allocator): add doc comments for panics and errors #21230
• refactor(allocator): fix unnecessary_safety_comment clippy warnings #21229
• refactor(allocator): fix unsafe_op_in_unsafe_fn clippy warnings #21228 👈 (View in Graphite)
• refactor(allocator): fix mut_from_ref clippy warnings #21225
• refactor(allocator): fix cast_sign_loss clippy warnings #21224
• refactor(allocator): fix cast_ptr_alignment clippy warnings #21223
• refactor(allocator): fix ptr_cast_constness clippy warnings #21222
• refactor(allocator): fix ptr_as_ptr clippy warnings #21221
• refactor(allocator): fix ref_as_ptr clippy warnings #21220
• refactor(allocator): fix borrow_as_ptr clippy warnings #21219
• refactor(allocator): fix unused_self clippy warnings #21218
• refactor(allocator): fix manual_div_ceil clippy warnings #21217
• refactor(allocator): fix map_unwrap_or clippy warnings #21216
• refactor(allocator): fix filter_map_next clippy warnings #21215
• refactor(allocator): fix single_match_else clippy warnings #21214
• refactor(allocator): fix inconsistent_struct_constructor clippy warnings #21213
• refactor(allocator): fix semicolon_if_nothing_returned clippy warnings #21212
• refactor(allocator): fix uninlined_format_args clippy warnings #21211
• refactor(allocator): fix lifetimes clippy warnings #21210
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent changes, fast-track this PR to the front of the merge queue

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[Copilot]

Pull request overview

This PR continues the allocator refactor by addressing Rust’s unsafe_op_in_unsafe_fn lint in oxc_allocator’s bump allocator implementation, reducing the need to globally suppress the warning and making unsafe operations explicit at call sites.

Changes:

• Remove the file-level unsafe_op_in_unsafe_fn lint expectation.
• Wrap unsafe operations (pointer dereferences, ptr::* ops, unreachable_unchecked, calls to unsafe fns) in explicit unsafe { ... } blocks to satisfy the lint.
• Adjust several allocator trait impl methods to call internal unsafe helpers within explicit unsafe blocks.

[codspeed-hq]

Merging this PR will not alter performance

✅ 48 untouched benchmarks
⏩ 3 skipped benchmarks¹

---

_{Comparing om/04-08-refactor_allocator_fix_unsafe_op_in_unsafe_fn_clippy_warnings (2b78e1e) with om/04-08-refactor_allocator_fix_mut_from_ref_clippy_warnings (40016e5)}

Footnotes

1. 3 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[graphite-app]

Merge activity

• Apr 9, 10:03 AM UTC: overlookmotel added this pull request to the Graphite merge queue.
• Apr 9, 10:11 AM UTC: Merged by the Graphite merge queue.