Henrique Bucher

The version check should be for 6.4.0 not 6.6.0 in some places. If you want to see when the interface changed, it's useful to use a website like below https://elixir.bootlin.com/linux/v6.4/source/include/linux/device/class.h

Guarantees can be made at every level. C++ relies on contract and context for safety as opposed to Rust. For example, when you sort a vector with `std::sort(vec.begin(),vec.end())`, that line...

Why do you think `arr.at(i)` should be used instead? Imagine what happens when `i` is an invalid index - it will throw and who will catch? It's going straight to...

I dont think this is fair. Rust provides security as an inherent feature, C++ does not. It is part of the language offering so fairness is to run the program...

From my user point of view, `DoNotOptimize()` means: do something with this lvalue such that it is a noop but the compiler will still think we are using it. So...

That all said, this is your library so the semantics of using it is what you say. I was surprised by it. If that's known and expected then it is...

The GLIBC team has a big team of core developers dedicated to the optimization of these base C library routines. You just can't get better than that. And they are...

I was wondering if the slow behavior was due to the absence of SIMD instructions or if the problem was the loads themselves. So I wrote code still within C++...

Actually, I believe the conclusion of the article should be the opposite: do not use SIMD with strings! That because 99% of the strings would be 128 characters or less...