crystal-z3 VS z3

Updated shard is in.

If everything went well, then the code should be in taw/crystal-z3 repo on github.

First, I decided to rearrange how code for this series is organized. All the episode code will go to this repo, and crystal-z3 repo will be the place where the library is going to live once it's a bit more ready.

All the code is in crystal-z3 repo, but there's no new code for this episode.

I put the code in crystal-z3 repo.

If you want something more complete, my Ruby Z3 gem is far more complete. Or you can use one of the official ones like Python's.

Z3 is a theorem prover library, and I maintain a Ruby gem for it. I wrote about it previously in 100 Languages Speedrun: Episode 23: Ruby Z3 .

The modern approach is to use general purpose programming language, and some kind of constraint solver engine (also known as theorem prover etc. - this field is really suffering from inconsistent terminology). In this episode we'll explore Microsoft Research's Z3. I didn't like any of its existing bindings, so I created Ruby bindings for it that I consider far superior, and we'll be covering this here.

I did this kind of work for Z3. No reason why it couldn't be done for other C libraries.