Skip to content

Policy: Should deprecated things be called out? #33

Open
@ehuss

Description

@ehuss

Should the spec ever mention that some language construct is deprecated? For example, things that we know are deprecated, but will not be removed in an Edition, or whose replacement is not yet implemented or certain.

Similarly, if something is removed or changed in an Edition, should the Edition-specific docs mention that a particular thing is deprecated?

  • ehuss's preference is to not mention that for Edition-specific changes. Non-edition changes are a bit more difficult to make a judgement on.

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