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

Warn when Cargo.toml contains keys we don't expect #13833

Merged

Commits on Nov 1, 2024

  1. Configuration menu
    Copy the full SHA
    eb36e5a View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    3db2b80 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    12622a9 View commit details
    Browse the repository at this point in the history
  4. cargo/interpreter: use alternate initializers for all manifest types

    This allows us to move a bit of the validation and fixing into these
    classes
    dcbaker committed Nov 1, 2024
    Configuration menu
    Copy the full SHA
    364aae7 View commit details
    Browse the repository at this point in the history
  5. cargo: Warn when encountering unknown keys

    Cargo sometimes adds new keys and Meson needs to gracefully handle
    those. Currently, an unknown key will trigger an uncaught Python
    exception, which is pretty much the worse case. With this change Meson
    will instead issue a warning much like the one for unknown cpu
    architectures.
    
    See mesonbuild#13826 for the motivation for this change
    dcbaker committed Nov 1, 2024
    Configuration menu
    Copy the full SHA
    408bde7 View commit details
    Browse the repository at this point in the history