Daniel Martí

From my node-schema talks with @warpfork, I've come to understand that a struct's MapIterator will only skip optional fields which are absent when one is using the node's representation. It...

You could also consider something like `io.Seeker`, where you can seek relative to the start, the end, or the current position. That seems like the most flexible, and only requires...

This would also give us more confidence with the added test coverage, I think. There are some refactors I want to do in the code generator, but I'm a bit...

I might surprise you with my take here: I don't think we should do this. I agree that avoiding pointers can be a good thing. Be it for memory locality,...

I mulled over this last night, and I agree with your conclusion. My points boiled down to: 1) not all schema types will be usable as Go map keys 2)...

I thought about that collision too, but it's actually impossible if we require the non-indexed version to use pointers. Because then, the first valid field would have to be `Index...

Here's another reason to do this: sometimes the pointers add unnecessary overhead of their own. For example: ``` type AnyScalar struct { Bool *bool String *string Bytes *[]uint8 Int *int...

We discussed this on Slack briefly, and then @warpfork and I talked about it again briefly today. First, to clarify the use case: ipld.Nodes are immutable. If you would like...

I'm not sure. This list of constants would correspond to the entire list in the multicodec spec, which is why I was assuming that `go-multicodec` should be called `package multicodec`....

This issue is inactive but still relevant, it should NOT be closed.