Possibly about to abandon the Effects chapter of TypeDD and properly explain the principles behind it instead. Much more useful, I think...
-
-
Replying to @edwinbrady
as long as you keep the "removing the hClose line is a type error" FileIO effect example...
1 reply 0 retweets 0 likes -
Replying to @robstewartUK
doesn’t need an Effects library chapter to do that… better to explain resource tracking in types generally
1 reply 0 retweets 0 likes -
Replying to @edwinbrady
Fair enough. Resource tracking in a multi threaded setting? Type check race between hGetLine & hClose? Concurrent resource FSMs?
1 reply 0 retweets 0 likes -
Replying to @robstewartUK
Files are hard like that. I’ll do some state machines and Hangman. Sticking to the basic principles.
1 reply 0 retweets 0 likes -
Replying to @edwinbrady @robstewartUK
Although I am planning an example of type safe message passing concurrency too
1 reply 0 retweets 1 like -
Replying to @edwinbrady
Seen the Haskell embedded session types HS'16 paper? Loosely related to Idris type safe message passing? http://homepages.inf.ed.ac.uk/slindley/papers/gvhs-draft-june2016.pdf …
1 reply 0 retweets 0 likes
I’m doing something much simpler here… I must read that though.
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.