Skip to content

Policy: How to deal with bugs in rustc? #32

Open
@ehuss

Description

@ehuss

Should the spec document actual rustc behavior (including bugs)? Or should it document the intended behavior? Or both?

Related: If there is a known issue, should it be encouraged or discouraged to link to the GitHub issue?

  • ehuss's preference is to never link to issues.

Related: Should it have specific callouts for future-incompatible warnings?
How should these known problems be documented? Should it document how it is intended to work? What if the intention is not yet known?

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