go-ipld-prime
go-ipld-prime copied to clipboard
ipld
Golang interfaces for the IPLD Data Model, with core Codecs included, IPLD Schemas support, and some handy functional transforms tools.
Hello! With codegen getting pretty advanced, I'd like to understand where generating fast path CBOR serialization/deserialization sits on the priority lists. I communicated some of my own findings a while...
The godoc on `ipld.Node` doesn't currently talk explicitly about memory usage, and it probably should. Some description I did of this in a recent issue is probably a good template...
was trying to understand data of an unknown schema, and wanted to load it into an `Any` node from cbor. got the following rejection: ` error: cannot match schema: union...
The semantic purpose of the `Prototype()` method on `Node` is to "give me enough information to create a Node that can reasonably replace this one" (where the meaning of "replace"...
It would be very useful to have a `schema/gen/go` schema that exercises the different types and edges of the schema (which schemaschema already does in a meta way), along with...
when working with large maps, it is quite likely for accesses to the map to happen across multiple interactions with that IPLD.Node object. Currently, the `Node`'s `MapIterator` interface does not...
Currently, the access pattern API provided for maps is to create a `MapIterator` which iterates through the items of the map. It would be useful to be able to iterate...
Let's talk about the codegen output size. Codegen is a useful tool. However, the lighter its requirements, the more useful and widely usable it becomes. Output size, if it grows...
Some interesting formations have appeared in downstream code as well as our own code: codecs have some common patterns and common segments of code, and then a fairly small section...
These are finding based on running a bench mark in go-graphsync. The benchmark simulates a single node getting a 10K file split in approximately 1K chunks from 20 different nodes...