DUX-5352 eval: Skip parsing commands in non-Haskell files#459
Merged
Conversation
To actually _execute_ eval commands with the proper bindings in scope, we need to be able to evaluate (interpret) a file, which requires we know its module _name_ (because `:module + *MODULE_NAME` only supports module names and not source paths). Let's guard adding an entry to the `eval_commands` map by making sure we can convert the path to a module name. See also: #458, #454.
lf-
approved these changes
Jun 15, 2026
parsonsmatt
approved these changes
Jun 15, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
To actually execute eval commands with the proper bindings in scope, we need to be able to evaluate (interpret) a file, which requires we know its module name (because
:module + *MODULE_NAMEonly supports module names and not source paths).Let's guard adding an entry to the
eval_commandsmap by making sure we can convert the path to a module name.See also: #458, #454.
docs/.tests/.