GitLab

The why3 configuration as never been satisfying, but the current state create even more problems.

To recall:

• before: after each update of Why3, the user needed to run rm ~/.why3.conf && why3 config
• now, it is not needed anymore but the system became too complicated to be correct

This issue propose to summarize which feature we want for why3 configuration (which one to keep, which one to remove) and to details solutions.

Possible features:

1. why3 knows which solvers the user wants to consider
2. why3 knows which shortcut are available
3. why3 knows which strategy are available
4. why3 knows which editor to use
5. works with different opam switch at the same time
6. keep configuration for new version of why3
7. IDE configuration
8. ability to add new configuration locally
9. ability to add new solvers
10. ability to add new strategy

Features kept:

Issues on the topic: #489, #518, #469 (closed)

This description will be updated with the discussion.