Skip to content

Rethink DSD #1059

Description

@MegaIng

Currently the DSD assumes a fixed number of potential results - if not literally, at least conceptually.

This is for example being violated by the DEFENDER_? roles introduced in #925. There are also decisions that return the number of robots, which while limited in practice does not really make sense to be handled that way.

It probably makes sense to rethink on how to handle this properly.

Ideas suggested in #925 by me:

  • ignore this? (hoping we only have one class of auto generated names which can be covered by ELSE)
  • Update DSD to support pattern matching or something?
  • Removing the extra index and unified all defenders into a single role name for the purpose of the DSD?

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

    No labels
    No labels

    Type

    No type

    Projects

    • Status
      📋 Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions