Uh oh!
There was an error while loading. Please reload this page.
Add --emit metadata - #37411
Conversation
With the same semantics as -Zno-trans
alexcrichton
commented
Oct 26, 2016
This isn't quite what I personally had in mind for this flag, but rather something like:
I feel like we definitely want a separate artifact here to avoid the compiler getting confused with "rlibs with code" and "rlibs with only metadata", and it'd also help build systems and such as it wouldn't all generate to the same file. |
nrc
commented
Oct 26, 2016
@alexcrichton that is a much bigger change, I'd want to be sure there was a big benefit to this. ISTM that we can get a lot of that benefit from just building into a different directory (e.g., Cargo could have a check directory in addition to release and debug). I had hoped we could keep a strict separation between code and metadata libs without having to rely on the file type. |
alexcrichton
commented
Oct 26, 2016
It is indeed a much bigger change, yeah. I do agree that the implementation of @brson will also likely have opinions on this as well! |
bors
commented
Oct 30, 2016
☔ The latest upstream changes (presumably #37400) made this pull request unmergeable. Please resolve the merge conflicts. |
nikomatsakis
commented
Nov 1, 2016
I also assumed (and would expect) a design like the one that @alexcrichton proposed. It is certainly a somewhat bigger change -- but not that much, right? |
nrc
commented
Nov 6, 2016
ping @brson - thoughts? |
nrc
commented
Nov 10, 2016
Closing in favour of #37681 |
With the same semantics as -Zno-trans
cc @rust-lang/compiler @rust-lang/tools
r? @alexcrichton