Skip to content

"Diagnostics: reporting errors and lints" #14

Closed
@nikomatsakis

Description

@nikomatsakis
Contributor

We should talk first about:

EDIT(mark-i-m): See #14 (comment)

cc @estebank

Activity

added
E-mediumDifficulty: might require some prior knowledge or code reading
on Mar 16, 2018
added
E-easyDifficulty: might be a good place for a beginner
and removed
E-mediumDifficulty: might require some prior knowledge or code reading
on Jan 23, 2019
pinned this issue on Jan 23, 2019
unpinned this issue on Jun 26, 2019
Karrq

Karrq commented on Jul 25, 2019

@Karrq

Looks to me like this issue is currently missing the following:

Errors:

  • How to find an error code and add an extended error
  • Conventions are how the error should be formatted (lowercase letter, etc)
  • when to use span_label etc

Lints:
Nothing? Maybe the section about removing lints present in the rustc Bug Fix Procedure could be added.

phansch

phansch commented on Aug 26, 2019

@phansch
Member

It might also be nice to link to the lint naming recommendations rules from RFC0344

2 remaining items

Loading
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

    E-easyDifficulty: might be a good place for a beginnerE-help-wantedCall for participation: extra help is wanted

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @nikomatsakis@rylev@phansch@Karrq@mark-i-m

        Issue actions

          "Diagnostics: reporting errors and lints" · Issue #14 · rust-lang/rustc-dev-guide