pacak

>> Hmm... Maybe, but this naming seems more natural in Haskell. Parser is a proper Applicative you can compose, while OptionParser is just an object you can run or transform...

> My perception is also colored by the [magazine article](https://rustmagazine.org/issue-2/applicative-parsing/) on the subject This was not a tutorial on `bpaf` though. This was based on a talk I gave about...

> I'd like to suggest you take this comment as an experience report about what I find complex rather than some objective claim over what is and isn't complex. Well......

I appreciate your feedback and will try to address it.

FWIW I updated the documentation and rewrote the tutorials. A simple parser that parses a single flag `-v` to get started with looks like this: ```rust fn main() { let...

> I feel like there are some disconnects happening when talking about the docs and APIs that some in person, sync conversations might help with. Sure. I'll see what I...

At this point I'd implement it something like this, with or without an optional helper inside `env_vars` ``` #[derive(Clone, Debug)] struct EnvVars { a: Option, b: Option, c: Option, }...

I pushed a `right-adj` branch that implements `start_adjacent()` method on parser trait. The idea is that the whole annotated block must be either directly adjacent to the beginning or to...

I'm looking into fixing it as well. On Tue, Jul 2, 2024, 16:33 Teoh Han Hui ***@***.***> wrote: > This is addressing the original issue, right? But what about the...

FCP for my change was approved :tada: Any ideas how to best implement it in `cargo`?