Add HELION_USE_DEFAULT_CONFIG env var to force use default config #37
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oulgen
approved these changes
May 13, 2025
a2b2272 to
f22a05a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added in #9,
use_default_configis very helpful when we care about the lowering part but not the performance part of the Helion kernel compilation workflow.It's common to want to run the examples in
examples/folder to quickly check if the lowering part is working, and with theHELION_USE_DEFAULT_CONFIGenv var introduced in this PR, we can easily do so without needing to go into the example file to manually adduse_default_config=True.