Been putting the finishing touches on Bunny's transformation into #fibers PR. One of the major things for me there is visualizing the changes, especially the breaking changes. For example switching from a promise based API to a fibers based API:
I implemented it and it works, but obviously blows up the memory. I've not finished a "Parallel Concurrent ML" paper and have a very little clue what I do in block-fn, I'll appreaciate if someone can give me a quick solution for now.
#Fibers provides synchronous ‘put’ and ‘get’ operations on channels (inherited from Concurrent ML?).
This can be problematic if the sender doesn’t trust the receiver: the receiver can trivially DoS the sender. I wonder how Spritely comrades deal with this? @cwebber@tsyesika@dthompson