Jerome Kelleher

Yes, I hope so. It does make me wonder if we should push forward the simple changes for allowing non-zero ancestral state and just jettison that complexity

Also review the changelog entries, they're pretty vague currently.

I think it's probably the same issue. Should be an easy fix with new macos-14 runner.

Assuming this is fixed in recent release

Has this been done already @lkirk? If so, we can remove the "future" label

Note: the only test that's failing is one that's poking into the details of parameter values. Everything else is passing fine.

Some quick notes here on using c11 atomics - getting things to compile on Unix platforms is easy, but Windows is problematic. It seems that MSVC doesn't support stdatomic.h, so...

Good to know. I guess that'll filter down to Python builds sometime around 3.15 or so (Python builds against specific MSVC, 14.x here for what we're working with).

@hyanwong @szhan @benjeffery - one thing to note here is that the last couple of commits remove the low-level requirement that the ancestral state must be 0. So we should...

I think this is something we need to merge in and release as part of tsinfer soon. I think we can expose the core functionality (do you divide by n...