Kauê Hunnicutt Bazilli

> Is there hope that this gets fixed soon? That is, prior to GC? As I understand reading through the code, this will only happen with GC, because partial strings...

One place that comes to mind is when using something like `bb_put/2`, like I did in the implementation of `phrase_from_stream/2`. In that case the partial string should not be backtracked,...

I think, however, that the copying from heap to the atom table could be very expensive, and that would make things such as `phrase_from_stream/2` artificially bad. In the long term...

From what I understood of #24, the partial strings are supposed to be allocated in the heap then? But what about my concerns about cases where the string shouldn't be...

Ok, going through the code it seems I'm not misunderstanding how the heap works. I think I now know what a `Ball` does though, which is doing that "copying to...

> So stuck there, I gather that is some rust issue. Yahk shaving… To compile and run Scryer from source, if that is what you were trying to do, you...

This seems to be the same as https://github.com/mthom/scryer-prolog/issues/1493#issuecomment-1854423876. If you change the order of `initialization/1` and `use_module/1` this works. It also works if you use a module such as `library(lists)`...

I can also reproduce this. ``` .../repos/dev/scryer-prolog> cargo --version cargo 1.70.0 (ec8a8a0ca 2023-04-25) .../repos/dev/scryer-prolog> rustc --version rustc 1.70.0 (90c541806 2023-05-31) .../repos/dev/scryer-prolog> uname -a Linux kbook 6.6.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Tue,...

The problem goes away when I compile with `--release`!!!

I updated to cargo and rustc 1.75.0 and it remains panicking, but only in the debug build. Maybe it's a debug assertion (so it goes away in the release build)...