Fix some visibility issues with mocking modules and foreign functions: #133
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.
When mocking foreign functions, the 'foreign ""' block is not a
module, and should not introduce an extra layer of visibility
modifications.
The visibility of the Expectation must always match the levels
argument of Expectation::new().
When mocking modules, the argument and return types of mocked
functions must be superfied by one level. Otherwise code like this
wouldn't compile: