my biggest issue with the vast majority of PL APIs is discoverability. for the most part, they work best if you literally skim every class/type/function/method/module you can and just... know them.
then there's Hoogle, which says "dream of a type and I shall provide a function."
Conversation
hands-down, Hoogle is the most impressive documentation resource I've ever found. I look at the types of data I've found myself with, mash in some arrows, and Hoogle says "someone implemented a library that does exactly what you want". it's glorious. every PL needs a Hoogle.
2
11
these thoughts brought to you by "I have a Vec and I'm sure there's a way to delete all its contents. delete_all? no, doesn't exist. drop? ah, that's a destructor. uhhh empty? destroy? clear? oh, it's clear! nice."
2
1
(admittedly I do not know by what type signature I could ever find this function, unless side-effects were encoded efficiently in the types. but it made me think about how much I love using Hoogle to find functions/operators when writing Haskell.)
1
1
IMO there's a ton of low hanging fruit in UI design for auto-generated docs. Here's a mockup I did for Rustdoc to address this exact issue:
3
3
Nice! I always wished that Rustdoc exposed the types more. I think older versions of the doc generation used to do that, but I could be misrecalling (it was a long time ago). At the moment types are often hidden behind an extra mouse-click, which can be a pain. 😔