Josh Triplett

@mark-i-m It sounds like you're interested in something different than this is proposing. @japaric is proposing a standard library that's equivalent to the current `std` but without linking to the...

As a separate thought, for a target like this, we could theoretically have a libc-compatible C library implemented in Rust, and then link C programs to that library. We don't...

> Should there be separate scopes for publishing a new crate and a version of an existing crate, instead of the single publish scope? Yes, please. I'd like to have...

@thomcc wrote: > That said it probably would be negligible compared to the cost of a system call, and the cost would be entirely in the error case The error...

The crates.io team plans to discuss this after the first of the year. One item we did have consensus on, though: this should definitely be a small team, not an...

On Sun, Jan 27, 2019 at 10:09:01AM -0800, mahkoh wrote: > - Please do not take my package names away without my consent. Please do not mischaracterize this RFC. This...

@dtolnay Still interested in pursuing this?

@tmandry Want to file a tracking issue, and add that to the RFC?

@nikomatsakis I feel like we shouldn't tie any kind of "you have to change your code" changes to updating rust-version; that would give people the (correct) impression of breakage when...

@Centril, @est31: Those are *exactly* the kinds of things I had in mind. I was partly inspired by recent discussions around `try` blocks and `throw`/`fail`; having postfix macros allows for...