Skip to content
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

rustc: Add a new -Z force-unstable-if-unmarked flag #41847

Merged
merged 3 commits into from
May 13, 2017

Commits on May 10, 2017

  1. rustc: Add a new -Z force-unstable-if-unmarked flag

    This commit adds a new `-Z` flag to the compiler for use when bootstrapping the
    compiler itself. We want to be able to use crates.io crates, but we also want
    the usage of such crates to be as ergonomic as possible! To that end compiler
    crates are a little tricky in that the crates.io crates are not annotated as
    unstable, nor do they expect to pull in unstable dependencies.
    
    To cover all these situations it's intended that the compiler will forever now
    bootstrap with `-Z force-unstable-if-unmarked`. This flags serves a dual purpose
    of forcing crates.io crates to themselves be unstable while also allowing them
    to use other "unstable" crates.io crates. This should mean that adding a
    dependency to compiler no longer requires upstream modification with
    unstable/staged_api attributes for inclusion!
    alexcrichton committed May 10, 2017
    Configuration menu
    Copy the full SHA
    99f629a View commit details
    Browse the repository at this point in the history

Commits on May 11, 2017

  1. Configuration menu
    Copy the full SHA
    af0e16c View commit details
    Browse the repository at this point in the history
  2. rustc: Remove #![unstable] annotation

    These are now no longer necessary with `-Z force-unstable-if-unmarked`
    alexcrichton committed May 11, 2017
    Configuration menu
    Copy the full SHA
    ab54f4b View commit details
    Browse the repository at this point in the history