I like articles like this that identify and address information gaps that aren't tackled by standard learning resources. Noticing these sorts of things that are just obvious to experts, because they picked them up over time, but are never explicitly explained to beginners, is a very useful skill.
Foo to Bar: Naming Conventions in Haskell
11–12 of 12 posts
Re: Foo to Bar: Naming Conventions in Haskell
#12Very good collection. To the standard type variables, I would add:
i for an index
s for state or stream
Also, in the context of lens specifically, s, t, u for the nth "containing structure" in the type signature.There's a funny story Kmett told about exploring abstractions until he wound up with a type parameterized by i m a s t a b u and deciding he should probably call it quits when the code starts threatening him.