Markus Triska

Thank you for all suggestions and comments! Almost everything would be better than the situation we have now, where the branches are presented almost as if they don't have anything...

The following may be a way out: We can simply add *all* `rebis-dev` changes in a **single commit** on top of master, by performing the following sequence of commands which I...

> But it also completely ignores/forcefully undoes all changes in master that are not in rebis-dev. To clarify: After these steps, **`master` is unchanged**! The only purpose of these changes...

@notoria, that's brilliant, thank you a lot! I tried this method and pushed the result to https://github.com/triska/scryer-prolog/tree/rebis-next . This branch looks **much better** in the sense that the number of commit differences...

Thank you a lot Mark for this awesome work! It now remains to ensure that `rebis-next` contains all changes from `rebis-dev`, and also all changes that have since been applied...

`rebis-next` looks good, thank you a lot! I suggest (force-)pushing this to `rebis-dev` and deleting `rebis-next` so that we can resume work on **`rebis-dev`** which several issues now already reference.

This is now vastly improved, thank you a lot! 

Yes absolutely, it would be great to have support for Trealla, one of the newest Prolog systems, also aiming for conformity to the Prolog ISO standard! The first consideration should be: What...

In this example, `clpz` is imported only locally in your own module, so not directly available from module `user`. I think it is the same in Scryer. One way to...

Could you please try to narrow this down to a smaller example? I started by trying to reduce the number of of `box/3` and `rotated_box/3` clauses, so that at least...