Stephen Blackheath

@clinuxrulz and @spockoyno - During the writing of the book, after careful consideration, I changed to the way it is now in the Java version. The Scala version hasn't received...

@spockoyno It would be great to get whatever you've done checked in. That transaction is left over from an older way of doing things. I just checked in a change...

I've created you a new repo at https://github.com/SodiumFRP/sodium-swift and sent an invitation to give you access to it, so please start off by checking it in.

``` java public void testHold() { StreamSink e = new StreamSink(); Cell b = e.hold(0); List out = new ArrayList(); Listener l = Operational.updates(b).listen(x -> { out.add(x); }); e.send(2); e.send(9);...

This is beyond awesome! Thank you!

A quick Google search tells me that Swift doesn't have a garbage collector... ...which presumably means that we will have problems with cleaning up smart pointer cycles? If so, C++...

In Javascript there are no finalizers or weak references so I am working on tracking all dependencies, which requires occasionally explicitly declaring variables captured in closures. There are also rare...

I don't think weak references help much with this problem but I could be wrong.

The problem will only occur if you use switch, and the code you're switching contains a CellLoop or StreamLoop. It'll leak memory and waste CPU time. So you can use...

@andrewbradnan The memory management will be wrong now in Swift, like was for Typescript (but fixed now) and still is for C++. I'll be implementing a fix for this in...