Eric Huss

Thanks for posting your writeup! I think it would be great to have a resource like that. Microsoft's own documentation is a little scattered and lacking, and having one place...

> If the apllication itself opts in, why is there an additional system wide opt in necessary for backwards compatibility? I think we can only guess, I haven't seen any...

Thanks for the heads up, indeed the license file has become very out-of-date. There are some issues tracking the general problem of license management and attribution at https://github.com/rust-lang/rust/issues/39897 and https://github.com/rust-lang/core-team/issues/8....

The current general meta-tracking issue for "what to do about licenses" is at https://github.com/rust-lang/leadership-council/issues/24.

I can try to clarify what is happening. Cargo keeps a cache of some rustc information such as its version stored in the target directory (`.rustc_info.json`). In step 5, cargo...

> Could you expand on the strangeness of the behavior? Just that the blank line solution seems potentially brittle. It assumes the data will never have blank lines. Also, it...

Thanks for the report! Can you say more about your use case? LTO only works for the final artifact, so it can't be set per-dependency. Is this maybe an executable...

Thanks for the report! I believe this is working as intended. The parser tries to adhere to [commonmark](https://spec.commonmark.org/0.31.2/) as closely as possible, and the [reference implementation](https://spec.commonmark.org/dingus/) agrees here. My guess...

I'm a little unclear to me how this would go from getting a `.crate` upload to accessing the repo associated with that published crate. Is the intent to use the...

I'm sorry for not responding sooner. I'm going to close since nobody on the team has the capacity to help with this at this time. I've followed up on #10662...