If you want docs on a #Haskell function or type, you have to do a web search on Hoogle or Hayoo! and then get single sentence docs mostly 2/
-
-
Replying to @alexelcu
Even for functions with unconstrained generic types, signature doesn't explain use-cases, e.g. :info on >>= (flatMap/bind) is useless 3/
2 replies 0 retweets 0 likes -
Replying to @alexelcu
Noticing an aversion for API docs in Haskell (also for
#Scalaz /#Typelevel), compare that situation with Java APIs: http://reactivex.io/RxJava/2.x/javadoc/ …3 replies 1 retweet 2 likes -
Replying to @alexelcu
In all fairness
#Typelevel libraries have a policy to provide type-checked docs, but that's not good enough, as it should mandate Scaladocs1 reply 0 retweets 0 likes -
-
Replying to @alexelcu
I like how Idris, despite allowing for more precise types, deviates from the Haskell trope of "types are a sufficient documentation".
2 replies 0 retweets 2 likes -
-
Agree with Tony. We only say that "type are documentation".
1 reply 0 retweets 0 likes -
and to the extent they are not, written prose is a desperate last resort, often counter-productive. There are overlooked middle grounds.
2 replies 0 retweets 2 likes -
Any suggestions on that middleground? I like both types and written prose, looking for more.
1 reply 0 retweets 0 likes
Property-based tests are a good starting point imo. There are also improvements on that, from there.
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.