Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ProblemDescription should be not mandatory #24

Open
EnricoMingo opened this issue Jan 18, 2019 · 0 comments
Open

ProblemDescription should be not mandatory #24

EnricoMingo opened this issue Jan 18, 2019 · 0 comments
Assignees
@alaurenzi
Labels
bug Something isn't working

Comments

@EnricoMingo
Copy link
Contributor

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.
@EnricoMingo EnricoMingo added the bug Something isn't working label Jan 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alaurenzi alaurenzi

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@EnricoMingo @alaurenzi