tart VS getargs

Here's another cool one: tart, for making things like ASCII diagrams for code comments (or hell, even fully fledged terminal art)

I wanted to see how Monodraw compared to my preferred terminal art editor (https://github.com/jtdaugherty/tart), but my version of macOS which is only a couple years old is apparently not supported anymore. Tart runs in the terminal, so it works pretty much everywhere. I think it deserves more users, so if you're not on macOS, maybe check it out.

better solution is tart

Source: Building the only piece of Haskell software I use, tart.

Actually, I would say getargs on this one. Full disclosure, I'm a major contributor to the library, but it is also faster than lexopt, and provides a bit more control.

I have benchmarked getargs to have significant performance gains from inlining.

I'd recommend getargs over argparse, it's also very well documented (but that version is not on crates.io yet)

It pains me that getargs 0.5.0 is still not released yet. If you can deal with a git dependency, I would highly recommend it, it can do exactly what you want with no fuss.

I'm currently working on bringing up getargs, which was abandoned on crates.io over 2 years ago. It has an API design that I agree with and I wanted to make it great, so I'm giving it a visit from the PR fairy.

If it's perfectly fine then it shouldn't be terribly difficult to write it in a way that the borrow checker is happy with. The problem is reformulating your problem such that it's easy to either annotate the lifetimes in that way or have the compiler infer them for you. And it's made more difficult if your libraries have incorrectly elided lifetimes.