Don Syme

@EverybodyKurts I think we'd better make you maintainer on this repo

Rewrite the plan and reassess Don't bother with these, you haven't been able to get to the bottom of these * https://github.com/Z3Prover/z3/issues/7036: qe_mbp.cpp assertion violation * https://github.com/Z3Prover/z3/issues/6871: algebraic_numbers.cpp assertion violation...

Here are your attemps which mostly haven't worked out well. DOn't try these again! - [Daily Backlog Burner: Add include directory for easier Z3 integration #7907](https://github.com/Z3Prover/z3/pull/7907) - [Daily Backlog Burner:...

Worked on Phase 2 documentation improvements by updating outdated Python API build documentation. Created PR with comprehensive rewrite of `src/api/python/README.txt` to provide modern CMake-based build instructions and eliminate confusion from...

## Plan Updated Based on Maintainer Feedback Based on your guidance to "rewrite the plan and reassess" and avoid the intractable assertion failures, here's the **revised strategic approach**: ### **Key...

Implemented **Phase 1 priority: Windows CI reliability** by addressing systematic access violation crashes in issues #7936/#7934. Created comprehensive solution with workflow separation and retry logic that unblocks development while enabling...

I'll close this and leave a note to focus on hashtable tuning and performance

Cool that you have your validation path resurrected. I remember from my theorem proving days that getting the balance right between investing in index creation and reaping reward in index...

@NikolajBjorner reopened as sounds like you want to investigate this one further?

I'll mark this as approved in principle. It should be possible define Slice and have the F# slicing syntax light up. Equally the SRTP workaround is pretty good!