Kauê Hunnicutt Bazilli

> Now what should happen with it in strict mode, according to you? I think the standard is pretty clear that it should always be _rejected_. > 5.1e) Offer a...

My guess is that it is prepared normally, but when executing and reaching `length(_,_)` it should either fail or throw an existence error. Is that not what "reject" means in...

> The whole point of this example is just to point out that it suffices to put predicates that are "implementation specific" extensions into modules. And strict mode (w.r.t. such...

Thank you for the in-depth historical explanation! > And 6.4 which talks about "some other implementation defined method" (6.4 end), and then in 6.4.4.2 illustrates what it meant by that...

> 1mo, what you call here implementation specific features are necessary to use the implementation defined mechanism. So the mechanism must be there, but — sorry — you cannot use...

The better word here would be "panic" I think, like in the error message. In the context of Rust it has a clear meaning, [though what it actually does on...

> Does this mean that memory overflows could be recovered that way? No, Rust just aborts on out of memory, which means it can't be caught. There are plans to...

> The best we can do now in stable is be really careful with [try_reserve](https://doc.rust-lang.org/std/vec/struct.Vec.html#method.try_reserve) or raw allocation calls, like is currently being done in many places in rebis-dev. Actually,...

> And I don't know how to pull in comments. You could look at how [DocLog](https://github.com/aarroyoc/doclog) does it, which is what generates the documentation at the Scryer Prolog site.

In the toplevel: ```prolog ?- A = ((>)(a). A = >(a). ``` Pretty weird.