Skip to content

Policy: Should the spec annotate or have callouts based on Rust release versions? #31

Open
@ehuss

Description

@ehuss

Should the spec ever mention Rust release versions, or differences between versions, or when something was introduced.

My preference is to never mention Rust versions. I think it generates clutter, which can balloon to a large amount of text. (Imagine if you annotated the entire document with description of what has changed and in which version, would likely end up marking up the majority of the document.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-metaCategory: Meta discussion about the repository itself. We should refine each use of the policy label

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions