Skip to content

Edition key should be per-target, not per-package #5661

Closed

Description

@nrc

Possibly optionally?

Activity

  1. alexcrichton commented on Jun 28, 2018

    @alexcrichton
    Member

    Seems plausible to me! That way existing crates could migrate one Target at a time instead of all at once

  2. dtolnay commented on Jul 29, 2018

    @dtolnay
    Member

    @dwijnand or @nrc, could you clarify for someone who is not familiar with Cargo what counts as a "target"? Would this allow selecting an edition at the granularity of individual top-level test files, or would that be a different feature request?

    [[test]]
    name = "rust2018"
    edition = "2018"

    I am interested in being able to test bitflags's support for being used in 2018-style macro imports, while keeping our existing 2015-style tests. See bitflags/bitflags#167.

  3. alexcrichton commented on Jul 29, 2018

    @alexcrichton
    Member

    @dtolnay your exact PR to bitflags is actually what @dwijnand's PR is enabling.

    "Targets" in Cargo are basically the same thing as "rustc invocations" or crates, so things like unit tests, libraries, binaries, examples, unit tests for librararies, etc, are all different targets.

  4. added a commit that references this issue on Jul 31, 2018
    4b95e8c
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

    P-highPriority: High

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions