AbstractNumericRightValue can be parametrized with different inner type#28
Merged
verhas merged 1 commit intoverhas:masterfrom Feb 9, 2020
Merged
Conversation
…pe, new method getNumericValue.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 change allows to implement RightValues compatible with Numeric but with other real class then Numeric. Example of such RightValues are LocalDate or EmptyValue. Real implementations based on this patch are in my branches empty_value and support_for_date2.
AbstractNumericRightValue can be parametrized with different inner type then Numeric based. New abstract method getNumericValue allows to get Numeric value.
Example of usage:
public class BasicDateValue extends AbstractNumericRightValue<Long, LocalDate> {
...
}
public class BasicEmptyValue extends AbstractNumericRightValue<Long, EmptyValue> {
}