Mattt

How would this approach handle multiple implicit arguments (e.g. `--input | $1` / `--output | $2`)? Could this behavior be delegated to `ArgumentSet` instead by saying that an `--expression` option...

I absolutely agree that we should support running doctest over multiple arguments in a single invocation. What I've been struggling with for this and `swiftdoc` has been how "Unix-y" (in...

@iainsmith Thanks for sharing your thoughts. I think that's a really helpful way to think about things! On the command line, there's a spectrum from generalized utilities to applications, and...

Thanks for the detailed write-up, @schwa. I was able to reproduce this locally. The reason that `answer` is unresolved is that the code block doesn't import the `Example` module. I...

#30 fixes this issue, but goes too far in its solution by running the entire source file ahead of any expectations (when not running with `--package` option). A more correct...

I agree that this would be a useful feature. I'd say the story for code generation in Swift is only "so-so" right now. Template-based systems like [Sourcery](https://github.com/krzysztofzablocki/Sourcery) have their uses,...

Looking at [a recent successful CI run for libgit2](https://github.com/libgit2/libgit2/runs/1883256768?check_suite_focus=true#step:4:64), I noticed that the output is different from what I get locally (`Generating documentation [0/70]` instead of `Generating documentation for v0.0.2...

> I'd say that this is a very common use case of this library. E.g. when you try to upgrade SwiftMarkup to use CommonMark version 0.5.0, then you will run...

I have another project that does just that: https://github.com/mattt/commonmarkattributedstring.

@larryonoff There's no API for it (yet), but it would be pretty straightforward to customize how things render by modifying this file in a fork: https://github.com/mattt/CommonMarkAttributedString/blob/master/Sources/CommonMarkAttributedString/CommonMark%2BExtensions.swift Alternatively, you could use...