Skip to content

refactor(allocator): fix unnecessary_literal_bound clippy warnings#21236

Merged
graphite-app[bot] merged 1 commit intomainfrom
om/04-09-refactor_allocator_fix_unnecessary_literal_bound_clippy_warnings
Apr 9, 2026
Merged

refactor(allocator): fix unnecessary_literal_bound clippy warnings#21236
graphite-app[bot] merged 1 commit intomainfrom
om/04-09-refactor_allocator_fix_unnecessary_literal_bound_clippy_warnings

Conversation

@overlookmotel
Copy link
Copy Markdown
Member

@overlookmotel overlookmotel commented Apr 9, 2026

Continuation of #21231.

Copy link
Copy Markdown
Member Author

overlookmotel commented Apr 9, 2026


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.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Removes the now-unneeded clippy::unnecessary_literal_bound expectation in oxc_allocator’s internal bumpalo_alloc module by making the CannotReallocInPlace::description return type explicitly 'static, matching its string-literal implementation.

Changes:

  • Drop clippy::unnecessary_literal_bound from the crate-level #![expect(...)] list.
  • Update CannotReallocInPlace::description to return &'static str (string literal), resolving the Clippy warning.

@codspeed-hq
Copy link
Copy Markdown

codspeed-hq Bot commented Apr 9, 2026

Merging this PR will not alter performance

✅ 48 untouched benchmarks
⏩ 3 skipped benchmarks1


Comparing om/04-09-refactor_allocator_fix_unnecessary_literal_bound_clippy_warnings (f13f5b1) with om/04-09-refactor_allocator_fix_redundant_closure_for_method_calls_clippy_warnings (5c79fe5)

Open in CodSpeed

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
Copy link
Copy Markdown
Contributor

graphite-app Bot commented Apr 9, 2026

Merge activity

@graphite-app graphite-app Bot force-pushed the om/04-09-refactor_allocator_fix_redundant_closure_for_method_calls_clippy_warnings branch from 889aafe to 5c79fe5 Compare April 9, 2026 13:16
@graphite-app graphite-app Bot force-pushed the om/04-09-refactor_allocator_fix_unnecessary_literal_bound_clippy_warnings branch from 00d5f77 to f13f5b1 Compare April 9, 2026 13:16
Base automatically changed from om/04-09-refactor_allocator_fix_redundant_closure_for_method_calls_clippy_warnings to main April 9, 2026 13:25
@graphite-app graphite-app Bot merged commit f13f5b1 into main Apr 9, 2026
37 checks passed
@graphite-app graphite-app Bot deleted the om/04-09-refactor_allocator_fix_unnecessary_literal_bound_clippy_warnings branch April 9, 2026 13:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-allocator Area - Allocator C-cleanup Category - technical debt or refactoring. Solution not expected to change behavior

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants