Calling getValue() on an uninstantiated variable throws an IllegalStateException
#957
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
…tateException + fix warnings
|
|
jgFages
approved these changes
Oct 26, 2022
|
Hmm. there is something wrong with the GH, all tests run on my machine |
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.
Calling
getValue()on a free variable returned its current lower bound.However, even if an assertion was present, a value could be returned, which could be confusing.
I propose throwing an unchecked exception, namely
IllegalStateException, when a call togetValue()is made on a free variable.This is safer and may also have some an educational value for beginners.