Skip to content

Conversation

@turbolent
Copy link
Collaborator

@turbolent turbolent commented Mar 31, 2023

  • Type parameter type bounds are optional
  • Parameter argument labels are optional: they should be encoded as empty string if not given

@turbolent turbolent requested a review from fxamacker March 31, 2023 23:33
@turbolent
Copy link
Collaborator Author

@fxamacker How could we document the second point in the spec?

@fxamacker
Copy link
Owner

@turbolent

How could we document the second point in the spec?

For both points, these optional values (nil for optional type and empty string for optional label) are allowed in the format by CDDL.

I think requirements like these (separate from the data format) can be mentioned as a consideration for CCF-based protocols in a non-CDDL section.

* [
name: tstr,
type-bound: type-value
type-bound: type-value / nil
Copy link
Owner

@fxamacker fxamacker Apr 1, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

UPDATE: based on slack discussion, we should remove nil from type-value and cherry pick to allow optionality only when needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants