Skip to content

inconsistent println! and eprintln! #478

@RobertMueller2

Description

@RobertMueller2

Version

1059c96

Description

We may write image to stdout, so IMO we should never place any other messages (mostly error messages) on stdout. But there are several places that use println! instead of eprintln!.

> grep -r "\<println" src | wc -l
11

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions