New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 0.4.3 #26
Merged
Release 0.4.3 #26
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
…ract clafers.
The model now has two roots: one is abstract, and the other is concrete. For example, consider the following model:
abstract A
B
abstract C : A
abstract D
E : C
F
This is represented in AstModel as:
abstract abstractRoot
abstract clafer
abstract A : clafer
B : clafer
abstract C : A
abstract D : clafer
E : C
F : clafer
root : abstractRoot
…in on function happens in a different order than usual.
…e values in initial propagation of join appears unexpectedly as an event in the incremental propagation.
…e values in initial propagation of join appears unexpectedly as an event in the incremental propagation.
…iority. For example, add "branchingPriority([[a,b], [c,d], [e]]);" to the Javascript will construct a ClaferOption with 1) Clafers a and b as the highest priority, 2) Clafers c and d as the second highest priority, 3) Clafers e as the third highest priority, 4) the remaining Clafers as the lowest priority. As usual, use the Javascript class to parse the input file. The parsed object (JavascriptFile) now contains an additional field for ClaferOption. This ClaferOption object must be passed to the compiler for the branching priority to take effect. For example: JavascriptFile p = Javascript.readModel(testFile); ClaferSolver s = ClaferCompiler.compile(p.getModel(), p.getScope(), p.getOption());
…avoid the possibility of divergence.
…o large for a 32-bit signed integer.
For example, for the expression a * b with a mulRange of {-2,...,2} will restrict the possibilities of a and b such that the product must lie in this range even if the multiplication is under a conditional. This will omit some potentially valid solutions. With the fix, you may notice more instances than previously if your model contains multiplication.
Previously, an expression a / b will always prohibit b = 0, even if the division is under a conditional. With this fix, you may see more solutions than previously found.
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.
branchingPriority([[a,b], [c,d], [e]]);