as long as you keep the "removing the hClose line is a type error" FileIO effect example...
-
-
-
doesn’t need an Effects library chapter to do that… better to explain resource tracking in types generally
- 5 more replies
New conversation -
-
-
effects here are really about combining resource protocols, rather than side effects. This is mostly why I dislike the library now.
-
that is, I've found capabilities and resource protocols would be better separated, when structuring large programs.
End of conversation
New conversation -
-
-
Also it'll age better when I inevitably change Effects yet again next month...
-
Save the Effects chapter for edition two. Hopefully Effects will be stable then…
- 2 more replies
New conversation -
-
-
This Tweet is unavailable.
-
Yes. Same problem - it’ll age too fast. Better to explain the principles and document the library well.
- 2 more replies
-
-
-
There’s no need for impure functions to achieve that. Descriptions of actions can have expressive, user defined, types.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
please explain the principles. Probably more difficult but in the end more satisfying for both the author and the reader.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.