-
Notifications
You must be signed in to change notification settings - Fork 66
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.
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
Support configuration via halmos.toml #125
Labels
enhancement
New feature or request
good first issue
Good for newcomers
help wanted
Extra attention is needed
Comments
karmacoma-eth
added
enhancement
New feature or request
good first issue
Good for newcomers
labels
Jul 19, 2023
This is a good feature. It would be nice to also have a |
5 tasks
karmacoma-eth
added a commit
to pillip/halmos
that referenced
this issue
May 23, 2024
karmacoma-eth
added a commit
that referenced
this issue
May 23, 2024
…ration file (#296) Co-authored-by: karmacoma <karma@coma.lol>
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature or request
good first issue
Good for newcomers
help wanted
Extra attention is needed
Problem
Currently, halmos only supports configuration via command line arguments. There are problems with this:
Solution
Having a config file that one can check in to version control would help with all these.
Halmos would first look for that config file, load these settings as a baseline, and then use command line arguments as an override.
Alternatives
Couple options:
[symbolic]
profile in foundry.toml, an approach seen in https://github.com/baolean/symexec-bench/blob/symtest/SymTest/foundry.toml(2.) is nice because it lets developers use a well known format, and the
[symbolic]
section feels right at home next to[fuzz]
, but I think overall I prefer (1.) because it reduces coupling with foundry. Foundry is nice, but it would seem weird to force users to use it if we support different frontends in the future (e.g. vyper)The text was updated successfully, but these errors were encountered: