fix Issue 22816 - [REG 2.099] Parser reads files with other extensions #13707
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.
I can't see any rationale for this looking up filenames with different extensions. Either
Module.read
or the driver already ensures that the filename already has an inferred extension for all file arguments from the command-line.All other uses of
FileManager.lookup
indmd.error
anddmd.expressionsem
will also either have a file extension or have been checked that it exists on disk before calling.No idea how to test this - I guess using dshell? It's important not to delay getting this in though, as it should not hit a release.