Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | refactor: improve propagation traceability | 2024-06-28 | |
| | |||
* | refactor: show semantics even if propagation fails | 2024-06-28 | |
| | |||
* | refactor(reasoning): fix Sonar warnings | 2024-06-28 | |
| | |||
* | refactor(language): improve propagation rule validation | 2024-06-28 | |
| | |||
* | refactor(generator): spelling | 2024-06-28 | |
| | |||
* | chore(deps): bump dependencies | 2024-06-28 | |
| | |||
* | fix(semantics): configure StateCoderAdapter | 2024-06-28 | |
| | |||
* | refactor(store): NeighborhoodCalculator API | 2024-06-28 | |
| | | | | | * Use US English spelling consistently * Avoid Eclipse Collections types on API | ||
* | interpreter: Fix NPE in VQE wipe/dispose -> EVM -> MatchUpdateListener chains | 2024-06-27 | |
| | | | | | | Port https://github.com/eclipse-viatra/org.eclipse.viatra/commit/a70e5e35f254079fbb0819731c81f64b3c79d1d7 from the VIATRA upstream repository | ||
* | refactor(docs): improve website formatting | 2024-06-25 | |
| | |||
* | fix(frontend): Algolia search | 2024-06-24 | |
| | |||
* | chore(frontend): fix peer dependency warnings | 2024-06-23 | |
| | |||
* | chore(deps): bump dependencies | 2024-06-23 | |
| | |||
* | build: publish Maven snapshots to GH pages | 2024-06-23 | |
| | |||
* | build: automate GitHub pages deployment | 2024-06-23 | |
| | |||
* | build: add Maven metadata | 2024-06-23 | |
| | |||
* | refactor(dse): expose state coder parameters | 2024-06-20 | |
| | |||
* | refactor(logic): fix Sonar error | 2024-06-19 | |
| | |||
* | refactor(logic): non-null aggregators | 2024-06-19 | |
| | |||
* | chore(deps): bump dependencies | 2024-06-17 | |
| | |||
* | fix: monomorphic matching for focus arguments | 2024-06-17 | |
| | | | | | | | | | Since we don't do pre-matching for multi-objects, there's no way to fire a decision rule with multiple focus arguments without creating a new concrete object for each focus argument, even if they match the same multi-object. To be more consistent with the multi-object case, we also don't allow the same concrete object to appear as two distict focus arguments. | ||
* | fix: allow predicates in rule actions | 2024-06-17 | |
| | | | | | We must mark any predicate definition in a rule action as mutable so that we can collect assertions created by rules during model generation. | ||
* | feat(language): warn about partial references | 2024-06-17 | |
| | |||
* | refactor(language): allow rules without preconditions | 2024-06-17 | |
| | |||
* | feat(language): validate quantification in rules | 2024-06-16 | |
| | |||
* | chore(deps): bump dependencies | 2024-06-01 | |
| | |||
* | refactor(reasoning): candidate view should always be a refinement of partial | 2024-06-01 | |
| | | | | | | | | | | Merge the candidate may/must queries with the partial may/must queries so that reasoning in the candidate model uses "Gentzen-style" assumptions about the candidate values of partal symbols that would be computed as unknown. This should not lead to performance degradation, because the corresponding joins were already being computed in the stopping criterion. In many cases, the extra clauses are immediately optimized away by the query optimizer anyways. | ||
* | feat: partial references | 2024-06-01 | |
| | | | | | References marked as partial are not concretized during model generation. The should be managed by the user manually using propagation rules instead. | ||
* | fix(reasoning): candidate count literal rewriting | 2024-06-01 | |
| | |||
* | feat: generate multiple solutions | 2024-06-01 | |
| | | | | | Switch to partial interpretation based neighborhood calculation when multiple models are request to avoid returning isomorphic models. | ||
* | fix(reasoning): candidate rounding mode | 2024-05-31 | |
| | |||
* | refactor(language): rule syntax | 2024-05-30 | |
| | | | | Make the rule syntax more similar to the predicate syntax. | ||
* | fix(language): validate unique rule names | 2024-05-26 | |
| | |||
* | fix(language): spurious exception in ProblemValidator | 2024-05-26 | |
| | | | | | Make sure getNodeArgumentForMultiObjectAssertion runs correctly even for ASTs with parse errors. | ||
* | fix(semantics): negative quantification in rules | 2024-05-26 | |
| | | | | | Make sure we appropriate quantify over the existence of objects in negative and transitive calls in rule preconditions. | ||
* | feat(language): node constants in rule actions | 2024-05-26 | |
| | |||
* | feat(dse): detect stuch propagation rules | 2024-05-26 | |
| | |||
* | feat: rule translation | 2024-05-26 | |
| | |||
* | feat(language): more extensive rule validation | 2024-05-26 | |
| | |||
* | refactor(language): merge Assertion and AssertionAction | 2024-05-26 | |
| | |||
* | feat(language): rule validation | 2024-05-26 | |
| | |||
* | feat: type checking for rules | 2024-05-26 | |
| | |||
* | feat: rule parsing | 2024-05-26 | |
| | |||
* | chore(deps): bump dependencies | 2024-05-26 | |
| | |||
* | fix(frontend): broken zoom: property in Firefox | 2024-05-26 | |
| | |||
* | chore(deps): bump dependencies | 2024-05-26 | |
| | |||
* | chore(deps): bump dependencies | 2024-05-04 | |
| | |||
* | feat(frontend): icon for error edges | 2024-04-28 | |
| | | | | Make error edges more visible even in black&white printouts. | ||
* | refactor(frontend): crisper zoom in WebKitGTK | 2024-04-27 | |
| | | | | | | | Use the non-standard zoom: property whenever available, because it gives a crisper result than transform: scale() in WebKitGTK. See https://developer.mozilla.org/en-US/docs/Web/CSS/zoom | ||
* | refactor(frontend): fix icon placement in Safari | 2024-04-27 | |
| | | | | Also affected WebKitGTK |