Günther Foidl

@Floccinaucinihilipilification11 this method existed in a (early) preview version of HW-intrinsics in .NET Core 3.0, which was later removed / replaced by `Vector256.Zero`.

> depends on how many issues you found At the moment no further (hopefully this remains so 😉). For the other findins, where no issues existed, I created one (e.g....

Are you using the managed client? Can you share more information so that [this issue becomes actionable](https://letmegooglethat.com/?q=how+to+write+a+good+bug+report)? With the info given nothing can be done, except refering to the https://github.com/dotnet/MQTTnet/wiki

@tannergooding I'd be happy if you could have a look on the use of xplat-intrinsics here. Thanks in advance!

> Maybe we could focus on making those as efficient as possible and ensuring they're sufficient to then delete this code? Next week I'll scan these codes and collect what...

For "I'll scan these codes and collect what APIs are missing so that this goal can be achieved." unfortunately I didn't had time so far, but it's scheduled as next...

Is there a (reasonable easy) way to build aspnetcore on top of a custom runtime-build? I'd like to build runtime based on https://github.com/dotnet/runtime/pull/75012, then use that build within aspnetcore for...

Let the 🌟 shine 😃 (/cc: @stephentoub) How it could look when StringUtilities is based on the runtime building-blocks w/o custom code here: https://github.com/dotnet/aspnetcore/compare/d2a1c23d90d4e69df47616b59b7215b3da8cc9f6...25c56209d2e3e8b9f8922b260aff5d2271f5d021 I didn't measure perf, just made...

`DefaultObjectPool` is thread-safe -- as well the use with `async/await`. `ObjectPool` is an abstract class, the provided implementation (`DefaultObjectPool` and the one specifically for StringBuilder) are thread-safe as well. But...

For casing...current code compares with `Ordinal`, e.g. https://github.com/dotnet/aspnetcore/blob/ff2148be7592be83f1f88e2f372ef04f02fdfdb8/src/Servers/Kestrel/Core/src/Internal/Infrastructure/HttpUtilities.cs#L250 (so that should be fixed according the issue?) Re-run the benchmark with leaving the `HttpUtilities.GetKnownMethod` from _main_ as is (case-sensitive), and making...