Tom Scogland

This does help with correctness in that sense, that's part of what we're trying to do here. There are a couple of different solutions we're exploring too, because this one...

One comment based on yours @publixsubfan, all previously existing raja atomics were relaxed. It's the stronger ones, and really the scopes, that are most interesting because they can mean we...

> Can you add something about how you get back non-atomic memory operations using this interface? When designing desul, we realized that the sequential option behaved more like a scope...

That looks pretty good. I'm working back through older emails today and saw the previous few all together. If it makes it easier, we could also use something like a...

Just to make sure I'm not giving @vsoch bad advice here, I think we can pull this together as a python-based jobtap plugin with cffi producing a regular plugin.so but...

Another thought here, I was reading through the `dependency-after` plugin and had a thought. That already implements all the functionality necessary for this, and most dependency resolution really, it just...

Oof, `after:` meaning `after-start` is a bit of a trip-hazard... I saw that in the code but didn't internalize it. That one's honestly rough enough I'd kinda be in favor...

Yeah, I think it would work for the more complex one too, so we might get the dependencies Stephen and I were discussing all that time ago.

> Yeah, I agree. This syntax was borrowed directly from Slurm for ease-of-transition, so it was darned if you, darned if you don't situation. Oh man, yeah that stings. At...

> Might be good to review [RFC 26](https://flux-framework.readthedocs.io/projects/flux-rfc/en/latest/spec_26.html) as part of designing this. That spec is a bit of a chimera - the openmp deps were defined earlier, but not...