You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bind meta wildcards to selected meta value once crate is chosen #68
In the library scanner, we should pull out any meta wildcards and bind them to the runtime meta requirements to satisfy. This way a user can say "use lib foo by symbolic name, but bind the compiled crate to whatever major.minor version of it you find"
Doesn't this happen automatically by virtue of the linkage metadata being encoded in the filename of the library? The crate will just request use std but we will link it to libstd-0.1-ABDCE and have to use that specific version forevermore.
Activity
graydon commentedon Jan 27, 2011
Shifted to rustc.
brson commentedon Mar 5, 2012
Doesn't this happen automatically by virtue of the linkage metadata being encoded in the filename of the library? The crate will just request
use stdbut we will link it tolibstd-0.1-ABDCEand have to use that specific version forevermore.graydon commentedon Apr 11, 2012
Yeah, this is now obsolete. Made sense only when we were still doing our own linkage. Note how old the bug is! Closing.
Merge pull request rust-lang#68 from oli-obk/master
ssse3 (rust-lang#68)
Add notes for cross-compilation to gcc-only targets (rust-lang#68)
Merge pull request rust-lang#68 from Hywan/patch-1
asm! support for the Xtensa architecture (rust-lang#68)
asm! support for the Xtensa architecture (rust-lang#68)
asm! support for the Xtensa architecture (rust-lang#68)
Add "ranjitjhala" and "carolynzech" to commitee (rust-lang#68)
asm! support for the Xtensa architecture (rust-lang#68)
asm! support for the Xtensa architecture (rust-lang#68)
Separate tests more and add another test (rust-lang#68)
Merge rust-lang#68
closure (rust-lang#68)