Fri3dNstuff

I changed to implementation to use the optimised version, @The-King-of-Toasters, thank you so much for the perf tests! there is still the question of expanding the width of the integers...

I just stumbled upon another manifestation of the issue, now with sentinel-terminated types: ```zig test { var x: [*:0]const u8 = "abc"; const good_ref: *[*:0]const u8 = &x; const evil_ref:...

fixed by #22243

Should `std.mem.absorbSentinel` keep the mutability of pointers? A returned mutable slice allows accessing the position of, and overriding the sentinel - which is probably unwanted... Though, the code below works,...

@alexrp My rationale to use the log of the size instead of the size itself is to show that the only values you find as the vector lengths are powers...

I've made [a PR](https://github.com/ziglang/zig/pull/24059) to make `std.math.ceilPowerOfTwo` (and friends) accept `comptime_int`s - when that'll be merged (assuming no issues there) I'll update this PR to use the changes.

This PR might be a good time to change the way `.items()` calculates its return type - the current way: ```zig switch (@TypeOf(&self.buffer)) { *align(alignment.toByteUnits()) [buffer_capacity]T => []align(alignment.toByteUnits()) T, *align(alignment.toByteUnits())...

the [recent changes to tuples](https://github.com/ziglang/zig/pull/21817) (suspected cause) now make the following code error (tested on `0.14.0-dev.2335+8594f179f`): ```zig test { _ = Foo; } const Foo = struct { // ^~~~~~...

> The improvement seems to be usage of `@shrExact` and `@shlExact` instead of `>>` and `