Markus Triska

The most serious technical shortcoming of SWI is described in https://github.com/SWI-Prolog/roadmap/issues/14. Other technical issues are: - incompatible term and goal expansion - incompatible `must_be` predicate for type checking.

Additional reasons are mentioned in #4. Since you have also contributed to the web page, I hope you can eliminate some of these problems, ensuring that CLP(FD) is presented in...

These are very good observations, thank you! Do these issues arise an actual use cases? The reason I ask is the following: Please tell me the (still reasonable) **most general**...

Please try the latest version: I have implemented this suggestion and would greatly appreciate your feedback.

So far, I have implemented specifically the cases you mentioned in your original post. For example, the following is now instantaneous: ?- X #= abs(X) + 1, X in 1..10000,...

Thank you a lot for looking into this! Yes, please do file a pull request so that the code is at least available! The dream is still to develop a...

I have installed experimental support for this in the `remote` branch: https://github.com/triska/ediprolog/tree/remote Please have a look, and I welcome all feedback about this! Thank you for your interest in ediprolog.

Can this be handled analogously to https://github.com/SWI-Prolog/swipl-devel/commit/044aabc5a8f2d801f233227622472e235e28310a ?

One important point for the immediate ad hoc solution: The default **prompt** that ediprolog uses is: `?ediprolog- ` . Please see: https://github.com/triska/ediprolog/blob/6f94bf2368a71490539db6020d7e4e9092c35a9c/ediprolog.el#L138 This is user-configurable, though I do not expect many changes...

ediprolog sets the prompt with `'$set_prompt'/1`: https://github.com/triska/ediprolog/blob/6f94bf2368a71490539db6020d7e4e9092c35a9c/ediprolog.el#L233 You can see the exact toplevel interaction in the buffer `*ediprolog-history*`. For example, in the case you posted: ?ediprolog- prompt(X, X). X =...