3 ms·
Regarding the Racket concurrency story, it has places; http://docs.racket-lang.org/reference/places.html http://docs.racket-lang.org/reference/places.html. "A
by logicchains 12y ago
Regarding the Racket concurrency story, it has places; http://docs.racket-lang.org/reference/places.html http://docs.racket-lang.org/reference/places.html.
"A place is a parallel task that is effectively a separate instance of the Racket virtual machine. Places communicate through place channels, which are endpoints for a two-way buffered communication."
So places are somewhat like Erlang processes.
Distributed Places are also interesting:
http://docs.racket-lang.org/distributed-places/index.html http://docs.racket-lang.org/distributed-places/index.html
- seabee 12y agoPlaces are about parallelism. For concurrency specifically, the most interesting features are threads, channels, and futures and can all be found here: http://docs.racket-lang.org/reference/concurrency.html http://docs.racket-lang.org/reference/concurrency.html Distributed places is pretty cool, however!
- MrBuddyCasino 12y agoThanks. So basically we get most of what Java has to offer plus thread mailboxes, which is nice. Not sure what to make of Places though - zeroMQ exists and has Racket bindings, is there something Places is better at?