Variants support #1

New Issue

perelman · 2024-07-01T18:05:18-04:00

perelman commented

2024-07-01 18:05:18 -04:00

It appears that interpreting one move at a time with knowledge of only the moves before/after is insufficient to interpret a dance as written on ContraDB. As a more complicated design the feature/variants branch instead allows interpreting a move multiple ways, passing all of the options along, expecting that some later move in the dance will not make sense under all of the variants, resolving which one was the right choice.

For a simple example of a move not determined by itself, consider a swing: normally it ends facing across unless the next move is up/down the hall.

(TODO: Add a more complicated example to this issue.)

It appears that interpreting one move at a time with knowledge of only the moves before/after is insufficient to interpret a dance as written on ContraDB. As a more complicated design the `feature/variants` branch instead allows interpreting a move multiple ways, passing all of the options along, expecting that some later move in the dance will not make sense under all of the variants, resolving which one was the right choice. For a simple example of a move not determined by itself, consider a swing: normally it ends facing across unless the next move is up/down the hall. (TODO: Add a more complicated example to this issue.)

Sign in to join this conversation.

No Label

No Milestone

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: perelman/contra-renderer#1