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."
-
Show this thread
-
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 replies 0 retweets 11 likesShow this thread -
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 replies 0 retweets 1 likeShow this thread -
(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 reply 0 retweets 1 likeShow this thread -
Replying to @pl_pierce
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:pic.twitter.com/SNuUbQ5rmw
3 replies 0 retweets 3 likes -
Replying to @wcrichton @pl_pierce
(also gave a general framework for generating these designs in https://arxiv.org/abs/2011.05600 )
1 reply 0 retweets 2 likes
Also GPT-3 powered doc search is *the* most obvious application of the technology. I would use that way more than Copilot.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
cognitive psychology. PhD