Asger Hautop Drewsen

> I guess the reasoning behind installing `base-devel` is that its packages are basically implicitly assumed to be installed in any PKGBUILD on the aur. After all, if you are...

I reported the bad error message to the Rust repository before I found this issue: https://github.com/rust-lang/rust/issues/145094

The problem seems to be the use of `async fn` in traits: https://blog.rust-lang.org/2023/12/21/async-fn-rpit-in-traits/#async-fn-in-public-traits Removing the `#[allow(async_fn_in_trait)]` from `FromConcurrentStream` also causes this warning, which explains the problem: ``` warning: use of...

> Honestly, decoding a token without validating the signature is something that you shouldn't do most of the time so I do not particularly care about making it user friendly...

> Well you can't really trust any of the things you see in the claims unless you validate the signature Sure, but I'm the client. I don't have access to...

The following C code produces such an error: ```c #include #include volatile int g_signal = 0; void signal_handler(int signal) { g_signal = signal; } int main() { pid_t child_pid =...

Yes, I agree for that specific example. My argument would be that if you have a `Vec` you can use `race_with_index` without having to allocate a new `Vec` to get...

> If we ever do make that breaking change, Float should only add distinct methods over its super traits. That was also my idea.

I have had a similar need in my own code. You can create an extension trait for `Numeric` which you can easily implement for all the types using a macro:...

This could also be implemented by using the `Array` trait from [`array-trait`](https://docs.rs/array_trait). Another option is to include the definition of your own `Array` and `Slice` traits, as these are also...