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

Lower the priority of unstable methods when picking a candidate. #48552

Merged
merged 6 commits into from
Mar 24, 2018

Commits on Mar 23, 2018

  1. Configuration menu
    Copy the full SHA
    1731bf8 View commit details
    Browse the repository at this point in the history
  2. When picking a candidate, consider the unstable ones last.

    If there is potential ambiguity after stabilizing those candidates, a
    warning will be emitted.
    kennytm committed Mar 23, 2018
    Configuration menu
    Copy the full SHA
    abf4d8b View commit details
    Browse the repository at this point in the history
  3. Changed check_stability to take an Option<NodeId> instead of `Nod…

    …eId`.
    
    This clarifies the intent of whether to emit deprecated lint or not.
    kennytm committed Mar 23, 2018
    Configuration menu
    Copy the full SHA
    0232744 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    28b2bba View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    db4f3f9 View commit details
    Browse the repository at this point in the history
  6. Configuration menu
    Copy the full SHA
    17cc3d7 View commit details
    Browse the repository at this point in the history