Commits on Dec 13, 2017

1. writeln!(stderr, ...) -> eprintln! …

   While working in other tasks, I noticed that there's a rather
   inconsistent way to handle errors. In some places we use `eprintln!` and
   in others `writeln!` to standard error.
   
   It seems like the use of `writeln!` don't have an strong motive, as the
   output is always to standard error, the lock is always handled the same
   than `eprintln` and there's no obvious (to me) optimization, so I
   decided to use the more idiomatic `eprintln!` everywhere.

   Agustin Chiappe Berrini committed Dec 13, 2017
   Copy the full SHA

   286cb9d View commit details

   Browse the repository at this point in the history