Java 8 predicates instead of specifications #74
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
adrienlauer
force-pushed
the
java8-predicates
branch
from
e59a3c7
to
d4080c9
Compare
|
I changed the *Verifier classes to *Asserter as asked. |
pith
approved these changes
Mar 13, 2017
|
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 PR removes Kametic specifications from the kernel, replacing them by Java 8 predicates. The intent here is to clearly separate the low-level class matching concern from the DDD specification concern.
This opens the way to work on Kametic specifications to be DDD-only specifications.
The main side-effect is that Java 8 is now required.