-
Notifications
You must be signed in to change notification settings - Fork 536
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce something about rmeta and metadata in general #468
Comments
@crlf0710 I don't actually know anything about rmeta or metadata. Who even is the expert? Is there at least a code snippet you can point us to? |
@mark-i-m Sure, there's the crate |
Btw, this is one of those areas I'd prefer refactoring into irrelevance - see rust-lang/rust#65407. |
@eddyb i believe metadata is the key to rust-lang/rust#65427, do you think this issue is worth resolving before the refactoring you mentioned, or are they orthogonal? |
I think they're unrelated, talk to Cargo people (e.g. @alexcrichton and @ehuss) about how pipelining works for But also, even without reusing the EDIT: oh, I found rust-lang/cargo#3501 (comment) - is the "metadata is different" part of that what you meant? It's technically true, but not for metadata reasons, but "does this crate need codegen and therefore information about codegen'd monomorphizations?" reasons. |
@eddyb ok thanks! Is it possible when you have time to give some brief introduction (in text, audio or whatever form) about the current status (or if the current status is not ideal, a sketch of new design) of crate metadata storage on disk and the metadata embedded into final rlib/dylib files. I'm eager to learn more about this, and it will be good include it as part of rustc-guide. |
I went ahead and wrote something up in #1044 on this. I realize things change over time, but I think a little information is useful. If anyone following this issue can give it a read, please let me know if anything is missing you'd like to see (or if you notice anything wrong). |
No description provided.
The text was updated successfully, but these errors were encountered: