Markus Triska

If this cannot be supported (yet) for `text` streams, then one option may be to make timeouts only work for **`binary`** streams? For binary streams, bytes can be read individually, and...

I see you now already implemented it also for `text` streams! Incredibly contribution, thank you a lot! If this works correctly, then it will tremendously increase Scryer Prolog's application opportunities,...

It looks very good! The only remaining small issue I noticed is in the test cases, and can be addressed at any time (also later): `setup_call_cleanup/3` may be useful to...

Thank you! The explicit module qualifications should not be necessary!

I now see the terminology "partial data" is still present: In the context of Prolog, "partial" is associated with "partially instantiated", from the documentation I would have thought the call...

And more importantly: returns partial data (distinguishable from EOF). On EOF, we get `[]`, and on timeout, we may also get `[]`, so how are the cases distinguishable? From the...

For completeness: We can always manually use **`at_end_of_stream/1`**, so `read_n_chars/4` itself need not even provide special facilities to distinguish this condition!

> suggestions on how to differentiate EOF vs timeout. Regarding the general API, I have now compared this with the Elisp function **`accept-process-output`**, which says: (accept-process-output &optional PROCESS SECONDS MILLISEC...

> However the immediate reason that comes to mind is a poorly behaved process could flood the server. Good point! What I was thinking about initially is an application with...

Great catch, thank you a lot for reporting this! Also for positive exponents: ?- format("~3f", [1.0e234]). 1.0e2 true. I think some way to reason a bit more about floats is...