Skip to content

have the spec and implementations agree on how tuple reprs support optional fields #369

Open
@mvdan

Description

The implementation at

// Optional fields for tuple representation are only allowed at the end, and contiguously.
says they are allowed as trailing fields:

// Optional fields for tuple representation are only allowed at the end, and contiguously.

However, the current spec at https://ipld.io/docs/schemas/features/representation-strategies/#struct-tuple-representation says:

Optional or implicit fields are not possible with the tuple Struct representation strategy, all elements must be present.

For now, bindnode follows codegen; see #368.

We should probably adjust the docs to agree with the codegen. cc @warpfork @rvagg

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

  • Status

    🗄️ Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions