Markus Triska

`copy_term/3` should wrap the gathering of residual goals in **`findall/3`** in order to undo any modifications that the gathering itself performs on attributes. Conceptually, `copy_term/3` should be written like this:...

Related issue #640.

0.9.0 is now tagged: https://github.com/mthom/scryer-prolog/releases/tag/v0.9.0 !

I second this: Tagging and releasing (on *crates.io*) `0.9.1` would be great: The latest version is from more than a year ago: https://crates.io/crates/scryer-prolog It was `0.8.127`.

Is this predicate useful on the Prolog-level? This seems to be an error that would most likely be thrown by the engine itself instead of by Prolog programs (within Prolog...

@Tachinid: One setting I suggest for ergonomic Emacs key bindings is to configure the `CapsLock` key to act as `Ctrl`. This can be made system-wide, and makes it easy to...

The `openssl` crate is currently only needed to perform a single operation: **scalar multiplication of a point on one of two elliptic curves**. This is used by `crypto_curve_scalar_mult/4` in Scryer...

The newly announced [**crrl**](https://github.com/pornin/crrl) library by @pornin may be a good candidate to resolve this issue, once support for `secp256k1` is added.

One application that comes to mind is [**Bitcoinolog**](https://www.metalevel.at/bitcoinolog/), which uses `crypto_curve_scalar_mult/4` to create Bitcoin public keys and addresses. It is true: If you need only an encrypted network connection, you can...

Thank you, well spotted! I took a look specifically at RustCrypto's [k256](https://docs.rs/k256/latest/k256/index.html) crate since it implements `secp256k1` which is needed for Bitcoinolog. It seems the crate almost provides the intended...