Tom van Dijk

Hi @clausecker, while probably migrating to C11 atomics is a good idea for portability, I do not yet understand why volatile is a problem. The reason I use volatile here...

With the `barrier_t` type, this could probably be implemented using C11 atomic types, although I'd have to read up on them first. However, the `must_suspend` is intended to be non-atomically...

@clausecker The whole `lace` part comes from a different project https://github.com/trolando/lace which I worked on 10 years ago. The idea here was to provide a fine-grained fork-join-style parallel framework, like...

So far I can partially modify Lace to use atomics instead of volatile variables, but I find that the generated code is less optimized. For example, Lace has a `tailsplit`...

It already is a union, it's just that for some reason the compiler now decides to compute the result via the stack instead of pure registers :(

I'll check this out later, what is the purpose of this version? I.e. use case?

Is there a use case where installing Sylvan into the OS is preferred over just pulling it using CMake or as a git submodule or something? I kinda cleaned up...

So currently in versions v.1.7.1 and beyond, I changed the build script of Sylvan to use FetchContent to get the Lace dependency. This was necessary to allow Knor to use...

This might also have been how I did it in my implementation, but I am not quite sure because I don't remember it like that. Or maybe I just came...

Quick response before I head out of the office to one particular thing, the "zdd_set_XXX" methods are a bit misleading as they are about the "domain sets" which are a...