Peter Mikkelsen

I agree 100% that having different internal representations for data, which can be used transparently from the prolog code is a great idea. At my day job, the APL interpreter...

Here is a backtrace. ``` peter@fedora:~/src/lpa$ RUST_BACKTRACE=full scryer-prolog test.pl thread 'main' panicked at src/repl_helper.rs:71:51: called `Option::unwrap()` on a `None` value stack backtrace: 0: 0x55de5f8debd2 - std::backtrace_rs::backtrace::libunwind::trace::h77485d2069ba1ee3 at /builddir/build/BUILD/rust-1.89.0-build/rustc-1.89.0-src/library/std/src/../../backtrace/src/backtrace/libunwind.rs:117:9 1: 0x55de5f8debd2...

Thanks, I will take a look and see if I can make some sense of it.

Okay, I think the general issue is that standard input is internally a `ReadlineStream`, and thus any attempt to read a character from that stream will enter the readline code,...

My guess would be that instead of "blindly" opening standard input as a ReadlineStream internally, we should attempt to check if standard input is indeed connected to a terminal first,...