Skip to content

Conversation

@overlookmotel
Copy link
Member

@overlookmotel overlookmotel commented Dec 18, 2025

Follow-on after #17022. AllocError type is pointless, as we never touch the contents of Result::Err. Remove it.

@github-actions github-actions bot added the C-cleanup Category - technical debt or refactoring. Solution not expected to change behavior label Dec 18, 2025
Copy link
Member Author

overlookmotel commented Dec 18, 2025


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.

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

This PR refactors the fixed size allocator by removing the unused AllocError type and replacing it with the unit type () in error results. As noted in the description, the AllocError type was pointless since the error contents were never examined.

  • Removed the AllocError struct definition and its Display and Error trait implementations
  • Simplified error handling by using Result<T, ()> instead of Result<T, AllocError>
  • Cleaned up unused imports (error::Error and fmt)

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@codspeed-hq
Copy link

codspeed-hq bot commented Dec 18, 2025

CodSpeed Performance Report

Merging #17077 will not alter performance

Comparing om/12-18-refactor_allocator_remove_allocerror_from_fixed_size_allocator (e8c0e07) with main (fb9e193)

Summary

✅ 42 untouched
⏩ 3 skipped1

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.

Base automatically changed from c/12-17-draft to graphite-base/17013 December 18, 2025 22:43
@github-actions github-actions bot added A-linter Area - Linter A-cli Area - CLI labels Dec 18, 2025
@overlookmotel overlookmotel changed the base branch from graphite-base/17013 to graphite-base/17077 December 18, 2025 22:48
@overlookmotel overlookmotel force-pushed the om/12-18-refactor_allocator_remove_allocerror_from_fixed_size_allocator branch from 024ab0a to e8c0e07 Compare December 18, 2025 23:02
@overlookmotel overlookmotel changed the base branch from graphite-base/17077 to main December 18, 2025 23:02
@overlookmotel overlookmotel self-assigned this Dec 18, 2025
@overlookmotel overlookmotel added the A-linter-plugins Area - Linter JS plugins label Dec 18, 2025
@graphite-app graphite-app bot added the 0-merge Merge with Graphite Merge Queue label Dec 18, 2025
@graphite-app
Copy link
Contributor

graphite-app bot commented Dec 18, 2025

Merge activity

…17077)

Follow-on after #17022. `AllocError` type is pointless, as we never touch the contents of `Result::Err`. Remove it.
@graphite-app graphite-app bot force-pushed the om/12-18-refactor_allocator_remove_allocerror_from_fixed_size_allocator branch from e8c0e07 to d37d728 Compare December 18, 2025 23:43
@graphite-app graphite-app bot merged commit d37d728 into main Dec 18, 2025
21 checks passed
@graphite-app graphite-app bot deleted the om/12-18-refactor_allocator_remove_allocerror_from_fixed_size_allocator branch December 18, 2025 23:49
@graphite-app graphite-app bot removed the 0-merge Merge with Graphite Merge Queue label Dec 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-cli Area - CLI A-linter Area - Linter A-linter-plugins Area - Linter JS plugins 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