Eric Myhre

*nod*. At some point I was holding the theory (think: "loosely held") that kind statements local to each use might be useful for sanity checking and good error messages. It...

The kind of error reporting case I'm think of is exemplified by: ``` advanced FancySomething { # ... } type FancyMapType {String:String} # one of these two is wrong type...

Thumbs up to both halves of that. > maybe that's a mode you describe in the advanced layout descriptor somewhere, "this thing behaves in this way, don't expect meaningful values"?...

As a tree of bullet points, forgive me if it's terse: - I'd suggest making `Kind` an enum (an actual enum, not a sum type), and making a `Node` "interface"...

I'm probably going to have to look at that repeatedly, but to first glance, I think that looks like it'll fly!

The `Key` type idea is really interesting. I'm not sure how it'll go. It's definitely not the same as we've done in golang, but it might work well. `Key` probably...

> @warpfork Correct me if I'm wrong here, my understanding is that the primary reason for the `Node` interface in Go is to allow minimal allocations whilst still allowing deserialization...

(Re-pasting from earlier discussion for reference availability) The purpose of this image is to make it crystal clear that someone implementing an IPLD library in a new language will want...

I still don't really understand the arguments in favor of removing ADLs from the picture. I estimate the odds that the concept of ADL will appear in the future and...

> I don't know if that is _the_ purpose Okay, fair. I should confine my statement to more like "It's what I had in mind in the earliest discussion". To...