runtimeverification / runtimeverification/evm-semantics
Introduce verbosity levels for `foundry-kompile`
Nobody has claimed this yet.
- Dominant language
- KCL
- Stars
- 591
- Forks
- 156
- Avg merge
- 2h 19m
- Merged PRs (30d)
- 1
Description
Related: https://github.com/runtimeverification/pyk/issues/521
Currently, the --verbose option in kevm foundry-kompile is not showing the detailed output for the kompile command that is invoked within foundry-kompile. Now that the --verbose flag is available in kompile (https://github.com/runtimeverification/pyk/pull/523), we might introduce different verbosity levels for foundry-kompile.
E.g., -v might include only foundry-kompile logs,
-vv — logs produced by both foundry-kompile and kompile, etc.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the foundry-kompile command and its invocation of kompile, then review the existing --verbose behavior and the related pyk issue and pull request. Done means verbosity levels consistently expose the intended foundry-kompile and kompile logs.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100