Skip to content

Comment on Clean Coder: The Dark Path (2017)parent

Comments

Yeah once you get into Monofunctor or 'PorcelainPile<static const volatile String&>' lawyering you know you went too far

TIL about Monofunctor.

Pretty nifty. It's for cases where your type is a container of something (as opposed to anything).

I.E. you can .map (or .Select if you're .NET-inclined) over the Chars in a String, but not some other type, because String can't hold another type.

https://hackage.haskell.org/package/mono-traversable-1.0.21....

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.