Josh Triplett

@Byron I think it's perfectly fine to skip uplifting for the initial PR, and we can re-evaluate it before stabilization. And if that allows skipping changes to the scheduler, that...

The problem is that each `Build` builds a separate library archive, and combining archives requires quite a bit of non-portable platform-specific knowledge. The ideal behavior would be to compile different...

@alexcrichton You do when you're building a library that other crates want to find by name, such as if you're constructing a static library and associated pkg-config files and headers...

Yeah, busybox `ar` isn't designed to create archives, only extract them. It isn't a usable implementation for compilation.

I don't think we should be making compiler-builtins GPL-with-runtime-library-exception. It seems like there's a version from LLVM that we could switch to, and keep the existing compiler-builtins license.

I feel like I'm missing some aspect of const semantics, but this seems like something that we should be able to catch at compile time by noticing that we've taken...

On Wed, Jun 24, 2020 at 11:57:26PM -0700, Ralf Jung wrote: > > In order for const eval to be able to read from files, we need to add a...

Following up on this: given how much we rely on crater to detect potential breakage, we really do need this. Would it make sense to try to seek out some...

Thank you *very* much for taking the time to implement this, and show how it could work with nightly Rust. I would prefer to avoid maintaining parallel support for nightly...

I sincerely hope that the version of `bstr` after 1.0 is simply `std` (or, more precisely, `core` and `alloc` as appropriate). Thank you for such a fundamental building block of...