On Wed, Jun 3, 2015 at 9:18 AM, Michael Tiedtke <michael.tied...@o2online.de> wrote: > Thank you! The set! primitive is atomic - that's good.
Just to be clear: when you are using futures with set!, you get the lower-level guarantees here, which do not include atomicity, indeed not even SC. > Futures and Places both are interesting concepts with implementations > and documentation. > > But what if I want to try my own model? Let's say, for example, tying true > parallelism to objects (by using environments, a special send and threads > in the usual sense without any further overhead by the runtime > environment if not my own? Racket's model of threads doesn't seem to > grant me that freedom anymore but the GUI toolkit - on the other hand - > already ties threads to top level windows and their event spaces. You would need to build them on top of either places or futures. (Or tackle the problem of making a new runtime system for Racket, I suppose. But I guess that's not necessary in this case.) > Racket is still a programming language where I can redefine define to be > 'null but I can't use low level threads as specified in SRFI-18? > (http://srfi.schemers.org/srfi-18/srfi-18.html) Racket is a programming language built by PL enthusiasts/researchers to do what we were interested in doing and to help us try to solve problems we wanted to solve. It isn't a finished product and if you want to build something with it or extend it, you are welcome to join in. That said, it isn't the right platform for everyone and there are many things under the sun. Best, Robby -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
