Skip to content

Questionable advice in bug report instructions #17848

Closed
@kmcallister

Description

@kmcallister

Noticed in #17824.

Your bug report instructions mention that "It's also helpful to copy/paste the output of re-running the erroneous rustc command with the -v flag", but since the -v flag causes rustc to print its version and exit, i am skeptical of this claim.

This is either a really odd way to ask for the version, or a bit of advice that's no longer relevant. What should we say instead? RUST_LOG=rustc rustc is a bit too verbose — I killed it after it wrote 8.1 GB of logs compiling fn main() { let x = 3u; }.

Metadata

Metadata

Assignees

No one assigned

    Labels

    E-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions