Stephen Celis
While the header and README provide guidance, there's nothing wrong with providing a little more.
Rather than: ``` usage: syn [options] ``` We could try to generate: ``` usage: syn [-nVaANdpP1ciCIHlvh] [-f ] ``` (We could alphabetize the flags, too.) We should consider the format...
Rather than: ``` -f, --file ``` We could generate: ``` -f, --file VALUE ``` We could support localizable strings for customization.
SwiftUI defines [`MutableCollection.move(fromOffsets:toOffset:)`](https://developer.apple.com/documentation/swift/mutablecollection/3348325-move/) and [`RangeReplaceableCollection.remove(atOffsets:)`](https://developer.apple.com/documentation/swift/rangereplaceablecollection/3349502-remove/) methods, which make it easy to interface with the [`onMove(perform:)`](https://developer.apple.com/documentation/swiftui/dynamicviewcontent/onmove(perform:)/) and [`onDelete(perform:)`](https://developer.apple.com/documentation/swiftui/dynamicviewcontent/ondelete(perform:)/) view modifiers. It'd be nice if the appropriate collections herein implemented the same...
Would there be any interest in updating Nimble's matchers to work using protocol extensions for discoverability? _E.g._, ``` swift // before expect(1 + 1).to(equal(2)) expect(1.2).to(beCloseTo(1.1, within: 0.1)) expect(3) > 2...
While I love that the A+ Promise gives us the ability to compose things in a functional context, I found that the current implementation requires quite a bit of monkey-patching...
A few folks have requested this. Would be good to add an optional "billing email" for the purpose.
See https://github.com/pointfreeco/pointfreeco/pull/326#pullrequestreview-166765184
- [ ] Transcript titles - [ ] Episode blurb (announcement email, etc.)
The README is very light on usage information and how jazzy parses documentation. Does it parse Markdown? reST? Which tokens does it support (in addition to `:param:`, `:returns:`)?