coot
coot
ok, the `TMVar`s come from `async` calls.
For me the property fails with a `Deadlock` when I comment out the `writeTQueue` action.
This is related to #1130
The difference is explained [here](https://ouroboros-network.cardano.intersectmbo.org/monoidal-synchronisation/Data-Monoid-Synchronisation.html#t:LastToFinish).
Let's wait with this PR until we decide how Genesis will be integrated.
In this case it's easy to build `ghc-tags-core` with either `ghc` or `ghc-lib` as a dependency. (`ghc-tag` and `ghc-tags-plugin` then depends on `ghc-tags-core`). I'd like to avoid two packages (as...
The above is just an initial draft which needs to be communicated with the `Daedalus` team, also note that we don't have `recovery` mode any more :), though we have...
> If these are delayed Would it help if you don't mark the thread which observes the value as racy? Then IOSimPOR will not take it into account and reorder...
And what about [`traceTVar`](https://github.com/input-output-hk/io-sim/blob/main/io-classes/src/Control/Monad/Class/MonadSTM/Internal.hs#L431-L476) or something similar? That's what allows to observe committed values to `TVar`s (~we could also add it for other data structures, since all shared variables are...
I think I got what you want to do in the QSM PR, basically: ```hs cresp IOSim s b -> IOSim s (a,b) ``` Then it could be used to...