refactor(allocator): InnerVec use Alloc trait

[overlookmotel]

Parameterize InnerVec (otherwise known as Vec2) and RawVec with Alloc trait introduced in #11198.

InnerVec and RawVec no longer have a dependency on bumpalo::Bump. The rationale for that is discussed in #11198.

The only substantive change this PR makes is that all Alloc methods panic/abort if allocation fails, rather than returning a Result::Err. This alters the behavior of try_* methods, which previously wouldn't panic. However, I don't believe we use any of those methods, and we have no plans to, so in my view we should remove them. In practice it should be very difficult to exhaust all memory, and if we did there's no way to gracefully recover from that (what would we do? only parse half the file?). So this has little/no practical impact.

That apart, this PR is pure refactor. The diff is large, but it's almost entirely adding the A: Alloc bound to all methods / iterators, and removing Bump.

[overlookmotel]

• fix(allocator/vec): fix unsoundness in Vec::extend_from_slices_copy #11200
• refactor(allocator): InnerVec use Alloc trait #11199 👈 (View in Graphite)
• refactor(allocator): introduce Alloc trait #11198
• 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 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.

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #11199 will create unknown performance changes

_{Comparing 05-20-refactor_allocator_innervec_use_alloc_trait (6827543) with 05-20-feat_allocator_introduce_alloc_trait (a2ab84b)}

Summary

🆕 38 new benchmarks

Benchmarks breakdown

	Benchmark	BASE	HEAD	Change
🆕	codegen[RadixUIAdoptionSection.jsx]	N/A	132.3 µs	N/A
🆕	codegen[binder.ts]	N/A	4.8 ms	N/A
🆕	codegen[cal.com.tsx]	N/A	38.9 ms	N/A
🆕	codegen[react.development.js]	N/A	2.2 ms	N/A
🆕	formatter[RadixUIAdoptionSection.jsx]	N/A	299.5 µs	N/A
🆕	formatter[binder.ts]	N/A	15.8 ms	N/A
🆕	formatter[cal.com.tsx]	N/A	128.1 ms	N/A
🆕	formatter[react.development.js]	N/A	8.1 ms	N/A
🆕	lexer[RadixUIAdoptionSection.jsx]	N/A	21.9 µs	N/A
🆕	lexer[binder.ts]	N/A	961.2 µs	N/A
🆕	lexer[cal.com.tsx]	N/A	6 ms	N/A
🆕	lexer[react.development.js]	N/A	397.3 µs	N/A
🆕	linter[RadixUIAdoptionSection.jsx]	N/A	2.8 ms	N/A
🆕	linter[binder.ts]	N/A	149 ms	N/A
🆕	linter[cal.com.tsx]	N/A	1.3 s	N/A
🆕	linter[react.development.js]	N/A	54.7 ms	N/A
🆕	mangler[RadixUIAdoptionSection.jsx]	N/A	14 µs	N/A
🆕	mangler[binder.ts]	N/A	797.9 µs	N/A
🆕	mangler[cal.com.tsx]	N/A	3 ms	N/A
🆕	mangler[react.development.js]	N/A	283.2 µs	N/A
...	...	...	...	...

ℹ️ Only the first 20 benchmarks are displayed. Go to the app to view all benchmarks.

[overlookmotel]

There's a small perf regression on a few benchmarks. I propose that we don't worry about it. Once we remove Result from signature of all methods in Vec, it'll be recovered.

[graphite-app]

Merge activity

• May 21, 12:42 AM UTC: Dunqing added this pull request to the Graphite merge queue.
• May 21, 12:50 AM UTC: Merged by the Graphite merge queue.