asnkit 1.1.0

Added

• asnkitcc convert, which decodes a value with one codec and encodes
  it with another, as JER to DER, with an .asni file or ASN.1 files
  it compiles first. asnkitcc now depends on the runtime asnkitrt.
• The compiler for browsers and Node.js, as WebAssembly, in
  packages/asnkit-compiler-wasm: it compiles and parses the text of a
  specification, and signs, encrypts, binds and gives a nonce as
  asnkitcc does. It is on npm as asnkit-compiler.
• The runtime for C, in packages/asnkitrt-c: the Rust runtime as a
  shared and a static library, with the header asnkitrt.h. It is
  built from source.

Changed

• asnkit-compiler builds for wasm32-unknown-unknown, where it has no
  module plugin, as WebAssembly runs no programs. aes-gcm is used
  without its default features, which the compiler did not use.

• The option embed of the plugins asnkit-gen-python and
  asnkit-gen-rust: with embed=false, the module made does not have
  the compiled specification in it, and is given one that is loaded
  from a file, as one that is signed, encrypted, bound or has a nonce.
  The module of Python then has use_asni().

Fixed

• XER, in every runtime: a BOOLEAN is read only as <true/> or
  <false/>, and anything else is an error, where it was read as false.
  An OCTET STRING with an odd number of hexadecimal digits is ended by a
  zero (X.680 22.3), so <A>123</A> is 12 30, where it was 01 23.
  A BIT STRING and an OCTET STRING may have space in them (X.680 12.10,
  12.12), and the runtime for Python no longer takes 0b, _ or + in
  a BIT STRING. A carriage return in a string is written 
, as one
  written as it is is read as a line feed.
• The playground no longer tells a byte offset for an error in JER or
  XER, which the runtimes do not give.