Skip to content

Rustdoc error messages are not consistent #38084

Closed
@ghost

Description

While playing around with rustdoc, trying to find some things out, most errors are not consistent, especially with the new error formatting. Also, since passes are well-defined, listing them can help, especially in an offline scenario.

A small example: (The last one has colours, per the new error format I presume)

$ rustdoc
expected an input file to act on
$ rustdoc --passes
Argument to option 'passes' missing.
$ rustdoc --passes foo src/bar.rs
ERROR:rustdoc: unknown pass foo, skipping
$ rustdoc --passes foo src/non-existing
error: couldn't read "src/bad.rs": No such file or directory (os error 2)

Metadata

Metadata

Assignees

No one assigned

    Labels

    T-rustdocRelevant to the rustdoc team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions