Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(allocator, data_structures, lexer, traverse): enable undocumented_unsafe_blocks clippy lint #9363

Conversation

overlookmotel
Copy link
Contributor

@overlookmotel overlookmotel commented Feb 25, 2025

Enable undocumented_unsafe_blocks clippy lint rule, and fix warnings it raises.

@github-actions github-actions bot added A-parser Area - Parser C-cleanup Category - technical debt or refactoring. Solution not expected to change behavior labels Feb 25, 2025
Copy link
Contributor Author


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 hot fixes, skip the queue and merge this PR next

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.

@overlookmotel overlookmotel marked this pull request as ready for review February 25, 2025 23:06
Copy link

codspeed-hq bot commented Feb 25, 2025

CodSpeed Performance Report

Merging #9363 will not alter performance

Comparing 02-25-chore_allocator_data_structures_lexer_traverse_enable_undocumented_unsafe_blocks_clippy_lint (4f2fc39) with main (e3b6eeb)

Summary

✅ 33 untouched benchmarks

@Boshen Boshen added the 0-merge Merge with Graphite Merge Queue label Feb 26, 2025
Copy link
Member

Boshen commented Feb 26, 2025

Merge activity

  • Feb 25, 9:04 PM EST: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
  • Feb 25, 9:05 PM EST: A user added this pull request to the Graphite merge queue.
  • Feb 25, 9:10 PM EST: A user merged this pull request with the Graphite merge queue.

…ted_unsafe_blocks` clippy lint (#9363)

Enable `undocumented_unsafe_blocks` clippy lint rule, and fix warnings it raises.
@graphite-app graphite-app bot force-pushed the 02-25-chore_allocator_data_structures_lexer_traverse_enable_undocumented_unsafe_blocks_clippy_lint branch from a44f650 to 4f2fc39 Compare February 26, 2025 02:05
@graphite-app graphite-app bot merged commit 4f2fc39 into main Feb 26, 2025
26 checks passed
@graphite-app graphite-app bot deleted the 02-25-chore_allocator_data_structures_lexer_traverse_enable_undocumented_unsafe_blocks_clippy_lint branch February 26, 2025 02:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0-merge Merge with Graphite Merge Queue A-parser Area - Parser 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