prataprc
First cut implementation is finished. ASTQuery is now in usable state, may be it is time to explore and document different ways of using ASTQuery on syntax-trees. Will keep this...
While at it, add support for white spaces in unicode, for instance SimpleScanner.SkipWS().
Skipping Unicode whitespace can be achieved by using SetWSPattern() API. By setting the necessary whitespace unicode-points. There is also unicode category called, `Separator, Spaces` http://www.fileformat.info/info/unicode/category/Zs/list.htm Can be used with golang's...
The example above is quite tempting to consider, it will cleanup lot of test code. But introduces additional dependency with packages with whom I don't have any line of sight....
I might choose to think array indexing as key-lookup where its index is a hash-able key, that is, array is always to be interpreted as [associative array](https://en.wikipedia.org/wiki/Associative_array) Otherwise array type...
> https://github.com/ipfs-rust/rust-ipld/blob/a2b6f30631bfd45a0ffdc78a9aa7e12c2b809f1e/core/src/ipld.rs#L8. @volker thanks for this reference. Actually thanks for the many references ;) I am kind of making this quick draft implementation to understand the specs in finer details....
> You could consider dropping everything but double precision, even on decode. In situation similar to IoT, where small embedded devices are expected to communicate using DAG-CBOR, do we assume...
> making a Node "interface" that is the container for actual values. Trait in rust is type-system-only concept. But there is something called `trait-object` that "kind of matches" with interface{}....
My bad, didn't realize that I will end up with [HKT](https://github.com/rust-lang/rfcs/issues/324) issue with (a), that is, parameterize` Kind` over `V`, and `M`. Will have to try (b). But that might...
After looking at the `Node interface{}`, able to understand why `Kind` was suggested to be simple-enumeration and not a sum-type. ```rust /// Kind of data in data-model. pub enum Kind...