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.

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

API - expose --experimental-codegen as --venom #4334

Closed
charles-cooper opened this issue Oct 27, 2024 · 2 comments
Closed

API - expose --experimental-codegen as --venom #4334

charles-cooper opened this issue Oct 27, 2024 · 2 comments
Assignees
Labels
enhancement Refactor Issues related to refactoring the codebase

Comments

@charles-cooper
Copy link
Member

expose --experimental-codegen as --venom in all compiler i/o (CLI, json input, output_bundle, source code pragma). it will be an alias for --experimental-codegen, but eventually we can promote it to be the preferred way.

@Philogy
Copy link
Contributor

Philogy commented Nov 4, 2024

Wouldn't this imply to some degree that Venom is no longer experimental?

@charles-cooper
Copy link
Member Author

charles-cooper commented Nov 4, 2024

Wouldn't this imply to some degree that Venom is no longer experimental?

kind of :)

it's going to be opt-in, but as of 0.4.1 it's looking like we've ironed out all the major bugs, and #4339 will help with assurances that it produces semantically equivalent code to the legacy pipeline.

it's still going to be "experimental" for some time especially as we keep adding more passes, but as we get more assurance from fuzz testing, symbolic testing and (tbd) audits, i think we can feel better and better about starting to take the training wheels off.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Refactor Issues related to refactoring the codebase
Projects
None yet
Development

No branches or pull requests

3 participants