Skip to content
This repository has been archived by the owner on Jun 29, 2022. It is now read-only.

Structural type encoding format #57

Closed
Stebalien opened this issue Apr 2, 2018 · 1 comment
Closed

Structural type encoding format #57

Stebalien opened this issue Apr 2, 2018 · 1 comment
Assignees

Comments

@Stebalien
Copy link
Contributor

Stebalien commented Apr 2, 2018

For L0, we need a format for encoding structural type definitions.

Requirements:

  1. Encoded in IPLD.
  2. Defined using L0 (where L0 defines a primitive type type).
  3. Allows compact value representation (but not necessarily compact type representation).
  4. Supports reflection, introspection.
  5. Supports code generation.
  6. Upgradable/extensible without consensus (i.e., no having to agree on field tags).

Good to have:

  1. Generics.
  2. Transformations (i.e., type definitions define transformations for upgrading/interpreting other types).
  3. Pointer/value distinction: allow embedding typed objects by value instead of only by pointer.
@rvagg
Copy link
Member

rvagg commented Aug 14, 2019

Closing due to staleness as per team agreement to clean up the issue tracker a bit (ipld/team-mgmt#28). This doesn't mean this issue is off the table entirely, it's just not on the current active stack but may be revisited in the near future. If you feel there is something pertinent here, please speak up, reopen, or open a new issue. [/boilerplate]

@rvagg rvagg closed this as completed Aug 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants