The println macro is not used to avoid string usage.
Dealing only with bytes allows us to be compatible with any encoding
and not just UTF8.
Later on, format macro will be made to have more readable code.
marmoute | |
Alphare |
hg-reviewers |
The println macro is not used to avoid string usage.
Dealing only with bytes allows us to be compatible with any encoding
and not just UTF8.
Later on, format macro will be made to have more readable code.
No Linters Available |
No Unit Test Coverage |
rust/rhg/src/commands/root.rs | ||
---|---|---|
24 | If stdout is closed, this will fails. We probably want a better error than that eventually. | |
34 | Maybe we use a bit more explicit error, like: "Error is RootNotFound, but no path provided" or soemthing in that flavor. | |
50 | Same feedback, there wil be legit cas were we cannot write to stdout and we should improve the errors here (and test theses case) | |
60 | What kind of error does Mercurial issue in this case ? Could we keep the same behavior ? |
Looks good. If I could nitpick some more, the description talks about WTF8, when it's UTF8 (because we're talking about String and not OsString).
If stdout is closed, this will fails. We probably want a better error than that eventually.