lexically scoped strictness #54
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
|
Sorry, completely lost track of this. thanks for the PR and the nudge! |
|
Thanks |
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.
This makes strictness lexically scoped, issue #53. It adds a 'nostrict' argument so that it can be turned off when it is already turned on.
The
$STRICT_MODEglobal no longer exists, instead there's a_strict_mode()method you can call to check what mode you are in.NB that the key name
Test::MockModule/...in the hints hash must not have the module name removed from it. The hash is shared amongst all loaded modules, and that's the convention to make sure various users don't trample on each others' data.