Ibraheem Ahmed

@Jensanf do you have the numbers for the `std` version?

#3225 does this for requirement errors, but we might be able to do this for more types of errors. e.g. "because foo is unavailable and bar is unavailable" could become...

Hmmm, miri doesn't support the membarrier syscall. I guess it should just use a regular fence under cfg(miri) then?

> Error: | = note: the `thumbv7m-none-eabi` target may not support the standard library = note: `std` is required by `winapi` because it does not declare `#![no_std]` This is odd,...

It seems `membarrier` is using an older winapi interface that presumably required std: https://github.com/jeehoonkang/membarrier-rs/issues/21. `membarrier` seems to be unmaintained... maybe we should just inline it? cc @jeehoonkang

Instead of a trait, `tap` could be a [postfix macro](https://github.com/rust-lang/rfcs/pull/2442) which would allow for things like: ```rust let x: Option = option .tap!(|x| dbg!(x)) .tap_matches!(|Some(x)| Some(x + 1)) .inspect!(|x| println!("{x}"))...

I think this can be solved by relying on matchit's tsr errors like axum used to, but only for routes that want that behavior. So the handler trait would get...

With the [release of 0.8](https://github.com/ibraheemdev/matchit/releases/tag/v0.8.0), the route parameter syntax has changed to use `{x}` or `{*x}`. You can escape literal `{` and `}` characters with `{{` and `}}` in static...

I think I'm the only person maintaining the site right now, I'll try to get to all the open issues and pull requests by next week. I don't think I...

I'd definitely appreciate help!