Refactor: None is not an ImportModule #3039
Merged
Conversation
This file contains 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
lukaslihotzki
force-pushed
the
option-importmodule
branch
from
650c825 to
c441f82
Compare
lukaslihotzki
force-pushed
the
option-importmodule
branch
from
ffae14c to
1b19d42
Compare
Liamolucko
reviewed
Aug 20, 2022
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.
ImportModule::Noneis neither a module nor an import. (What would its contents or itsfrompart be?) Therefore, the correct name for ImportModule would be ImportModuleOption, orOption<ImportModule>in idiomatic Rust. Also, this change allows to enforce non-Nonemodules by the type system, which is handy, but not strictly needed, for #3019.