Andy Polyakov

There might be some misunderstanding on my[?] side. You'd use `cargo:rerun-if-changed` in case you find that rebuilding upon **any** change in `cargo package --list` excessive. But either way, the suggested...

> Because pkg_config is emitting `rerun-if` commands, the default behaviour you mention may not be as expected. Bingo! If you have one `rerun-if`, you need all of them. And that's...

Just in case, as for o-wasm label. It's actually two-part now, wasm and Windows. And as discussed in the commentary, it's possible to make a case for extending the approach,...

Could you describe how do you envision it would work in a build script? Would I call `windows_registry::find("clang-cl")` in order to figure out if it's installed [as part of VS]?...

Here is the thing. Which qualities make a sequence of bytes to a signature? Or alternatively, can one call a sequence of bytes a signature if it's same value for...

> BLS spec [says] (0

> SK==1 Question I'm struggling with is a little bit more subtle. Yes, from forging viewpoint SK==0 and SK==small_n are equally bad. But trouble is that specifically SK==0 facilitates _retrospective_...

> Hence signing [with secret key 0] Quoting wikipedia, "A valid digital signature [...] gives a recipient very strong reason to believe that the message was created by a known...

> Come to think of it, it might be good to suggest (but probably not require) fixing the most significant bit of the secret key to 1. Has negligible effect...

Upcoming swig 4.1 will support node.js v6 through v15, and presumably even v16. There is a remaining issue with Workers, and it's being worked on. Other than that, our github...