Skip to content

edge representation change needed #24

Description

@nmorse

Growing out of the array representation of edges. It was small and succinct, but once some overloading of positional meaning started to be necessary, that was the first nail in the array based coffin.

  • position 0 -> from
  • position 1 -> to
  • position 2 -> type
  • position 3 -> name
  • position 4 -> guard or alias
  • position 5 -> index?

also needed for set and set edges is sub_type:"op" enum:["push", "pop", "enqueue", "dequeue"]...

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions