bstrie

Can this be merged?

If you can narrow it down at all (and possibly even if you can't), please file a performance regression bug at https://github.com/rust-lang/rust/issues .

Note that the RustCrypto project has their own constant-time base64 crate (https://crates.io/crates/base64ct), so if this crate were to gain constant-time support then perhaps they would be willing to deprecate their...

This is complete. It's possible that we may find that we can archive even more repos as we continue to regularize the Enarx organization's Github presence, but those will be...

@stephssmiths It looks like there is a project out there that seeks to achieve a similar result: https://github.com/Shnatsel/rust-audit . Care to take a look at it and see how it...

There's also a proposal here for Cargo to have first-class support for this: https://github.com/rust-lang/rfcs/pull/2801

On behalf of the Edition 2024 Working Group, even though our soft deadline for accepting editions changes has passed, we're still willing to entertain changing the SIGPIPE default in the...

> make it so users can never write LazyCell or LazyCell T> - so we could eventually drop the second parameter in a background-compatible way I somewhat doubt it would...

I would like to consider alternative 7, the extended shebang. I don't think the backticks and the redundant `cargo` specifier should be necessary, producing this: ``` #!/usr/bin/env cargo # [dependencies]...

The frontmatter syntax wouldn't need to be added to Rust's grammar, correct? In other words, the frontmatter parsing would be a preprocessing stage solely within Cargo, which would strip out...