Diggory Blake

I think there's a nugget of value in this RFC: specifically a set of "higher standards" that crate authors can choose to follow, where those standards are agreed upon in...

> Giving maintainers of popular crates the option Yeah I'm not opposed to giving the option, as long as it's not a requirement.

This branch adds a method to remove parameters from the request: https://github.com/tokio-rs/axum/compare/main...Diggsey:axum:axum-v0.7.7-patched?expand=1

It would solve my use-case, but I think it could be confusing. Especially if `Path` continues to be the "default". Axum already hides what constitutes a single router - for...

I ran into another use-case where I need UrlParams to be public: I want to attach the extracted URL parameters to the request's tracing span. I can't use `RawPathParams` because...

There's also two types of global _toolchain_ installation: 1) A shared set of toolchains between all, or a group of users, that any user in that group can modify. 2)...

@brson What do you think of this strategy: **Non-windows:** - Relax anti-sudo check, so that it succeeds if `$UID` *or* `$SUDO_UID` corresponds to the correct home directory, but it will...

@vi I was focusing on global toolchains in the style of npm, where root *is* required to install globally. You seem to be suggesting a different feature - the ability...

@vi You might want to take a look at what @RalfJung is currently doing - https://github.com/rust-lang-nursery/rustup.rs/pull/1141

@vi I'm not sure I follow: we were talking about a shared `RUSTUP_HOME` directory, but cargo doesn't put any files there. If there are no rustup changes to make, then...