Skip to content

Bind meta wildcards to selected meta value once crate is chosen #68

Closed

Description

@graydon

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"

Activity

  1. graydon commented on Jan 27, 2011

    @graydon
    ContributorAuthor

    Shifted to rustc.

  2. brson commented on Mar 5, 2012

    @brson
    Contributor

    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.

  3. graydon commented on Apr 11, 2012

    @graydon
    ContributorAuthor

    Yeah, this is now obsolete. Made sense only when we were still doing our own linkage. Note how old the bug is! Closing.

  4. added a commit that references this issue on Jul 19, 2017
  5. added a commit that references this issue on Oct 23, 2018
  6. added a commit that references this issue on Dec 9, 2021
  7. added a commit that references this issue on Aug 21, 2026
  8. added a commit that references this issue on Sep 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-frontendArea: Compiler frontend (errors, parsing and HIR)A-linkageArea: linking into static, shared libraries and binariesA-runtimeArea: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions