Skip to content

ProblemDescription should be not mandatory #24

@EnricoMingo

Description

@EnricoMingo

In a general (bad) design, the problem description could be hardcoded inside a particular solver implementation. Despite this is not good, anyway it is possible therefore the needs of a problem description should not be mandatory imho.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions