Keags

I'm once again closing this since protofsm's design is still being stabilized and significant effort has been invested into polishing #8270

> Any updates on this since last year? What updates are you looking for specifically?

Still relevant

I'm taking this to mean a PR will be accepted that implements it manually.

Is there a way to prevent the export of the individual enum constructors and use smart constructors that forbid the use of NaN and Infinity? That's the way I'd do...

So it appears Rust does not support private constructors for enums. I will adjust the PR to newtype f64 into a value that ensures finiteness.

I guess where I'm tripping up is where is the transformation from the concrete data type to the IPLD DM taking place? It doesn't seem to occur anywhere. The above...

I just find it rather confusing that the documentation talks a lot about the IPLD data model but that the implementation just uses serde. If we're just gonna use serde,...

I feel like I have to be missing something really important. Can you explain why IPLD should have *anything* to do with serde? serde has an entirely separate data model...

Here's how it is defined by the protobuf3 spec: https://developers.google.com/protocol-buffers/docs/proto3#packages I suppose the question is that if I were to submit a patch, what modules would I begin looking in...