Rust Lang

139 readers

1 users here now

Rules [Developing]

Observe our code of conduct

Strive to treat others with respect, patience, kindness, and empathy.
We observe the Rust Project Code of Conduct.
Submissions must be on-topic
Posts must reference Rust or relate to things using Rust. For content that does not, use a text post to explain its relevance.
Post titles should include useful context.
For Rust questions, use the stickied Q&A thread. [TBD]
Arts-and-crafts posts are permitted on weekends.
No meta posts; message the mods instead.

Constructive criticism only

Criticism is encouraged, though it must be constructive, useful and actionable.
If criticizing a project on GitHub, you may not link directly to the project’s issue tracker. Please create a read-only mirror and link that instead.
Keep things in perspective
A programming language is rarely worth getting worked up over.
No zealotry or fanaticism.
Be charitable in intent. Err on the side of giving others the benefit of the doubt.

No endless relitigation

Avoid re-treading topics that have been long-settled or utterly exhausted.
Avoid bikeshedding.
This is not an official Rust forum, and cannot fulfill feature requests. Use the official venues for that.

No low-effort content

Showing off your new projects is fine

No memes or image macros

Please find other communities to post memes

No NSFW Content

There are many other NSFW communities, let’s keep this related to the language

founded 1 year ago

MODERATORS

[email protected]

Experimenting with better CLI errors (lemmyrs.org)

submitted 1 year ago by [email protected] to c/[email protected]

4 comments fedilink hide all child comments

What do you think about this kind of indication for conflicting or otherwise invalid arguments?

With command line arguments being 1D and line length valid up to hundreds of kilobytes only inline indication seems to work.

Would you change anything?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 4 points 1 year ago (1 children)

I'd recommend adding the markers on a line below the text, in a similar way to how rust compiler output indicates errors.

Also WIN isn't really clear to me what it's supposed to mean, does it mean that flag "wins" and takes precedence over the other conflicting flag? Does that even matter if the program exits with an error anyway?

[–] [email protected] 1 points 1 year ago

I’d recommend adding the markers on a line below the text, in a similar way to how rust compiler output indicates errors.

It is easier for the rust compiler to do so since rust files are always valid utf8 and formatted to be of reasonable size. Doing the right thing with OsString is harder, plus lines can be long and trimming it enough that it still fits on a line above all that while also dealing with unicode shenanigans... That's why I'm trying to do things inline where most of those things

Also WIN isn’t really clear to me what it’s supposed to mean, does it mean that flag “wins” and takes precedence over the other conflicting flag?

Right. Wording can use more work :)

Does that even matter if the program exits with an error anyway?

Hmm... Interesting question. I guess it is less useful in this case but I can imagine some stranger situations. Plus I'm trying to create more detailed/user friendly error messages - one is text description "FOO is required" and the other one shows place where exactly this "FOO" is required.