Markus Triska
Markus Triska
The best way to reason about variables within your program is to choose a good representation for your data. In an initial conversion step, you will likely need impure checks...
Association lists are a fine and also very portable way to do such lookups, and their performance is often completely acceptable. Dicts may be useful if you do a let...
Thank you a lot!
The current `master` branch implements changes related to this issue, could you please try it?
Does merged #1907 resolve this issue?
This is now available in `master`, and I think this resolves this issue.
@matt2xu, @razetime: The most important section for this is in `system_calls.rs`, specifically in: https://github.com/mthom/scryer-prolog/blob/de10ccfdeea33abb5d64d5a4bc33ee39b14ab002/src/machine/system_calls.rs#L6136 For comparison, the HTTP server already uses `tokio`: https://github.com/mthom/scryer-prolog/blob/de10ccfdeea33abb5d64d5a4bc33ee39b14ab002/src/machine/system_calls.rs#L4323
Can the ideas from #1998 be used to make this also work for `socket_server_accept/4`? (@aarroyoc ?)
Yes, you can work around this for example with: **`M-: (setq ediprolog-temp-file ".ediprolog") RET`**, so that a local file is used to consult the program!
Thank you a lot for looking into this, I greatly appreciate your help!