Skip to content

Literal representations used in Arcs should use a type table #7138

@shans

Description

@shans

(from b/172170292)

Currently each literal of a Arcs Manifest states the handle type for each handle inline. This leads to repetitions and deep / recursive types have equally deep + recursive literal representations leading to stack over flows.

Ideally, a table would be used to describe each type allowing a smaller representation that is more general (supporting nesting/recursion).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions