Markus Triska
Markus Triska
Another recent example of the system silently losing solutions, **the worst kind of incorrectness**: #2272.
Another recent example, once again due to the way strings are currently implemented, making it easy to forget handling them in certain branches because their handling is spread over so...
This seems to be a candidate for a **representation error**, because the syntax is correct. 7.12.2 Error classification ... f) There shall be a Representation Error when an implementation defined...
Related: #2180.
The key advantage of heap allocation is fast reclamation of memory on backtracking, using **constant time**!
The internal encoding should be fixed to UTF-8, since supporting different internal encoding variants for strings is too error-prone. Conversion to a Rust string may only be needed in comparatively...
Personally, I think the **space saving** is not worth the effort, but there is a different interesting advantage that a dedicated encoding specifically for octets could yield, if it guarantees...
One general comment about this issue, also directed to authors of other Prolog systems so that they can learn from the experience we gain here: Implementing or retaining an *ad hoc*...
With #2370, another issue that seems related to the current representation has now appeared. @mthom, @bakaq ... please ... save us!
Another such case is #2381.