source: me having to wade through someone else's package comprising 10-20 tiny modules split along arbitrary boundaries that only make sense to the person who authored them
Principal engineer at Mercury. I've authored the Dhall configuration language, the Haskell for all blog, and countless packages and keynote presentations.
I'm a midwife to the hidden beauty in everything.
💖 @wiredaemon
source: me having to wade through someone else's package comprising 10-20 tiny modules split along arbitrary boundaries that only make sense to the person who authored them
You won't believe how she solved the orphan instance problem with this one weird trick!
i feel like the main thing that gets in the way of me doing this in haskell is how record fields all end up directly in the module's namespace. but i sure as hell do this in rust
How does this interact with the *.Internal approach of having a separate testable module and a main modules which only exposes the safe and stable bits?