Skip to content

253 the recoverable operator mechanism is buggy#256

Merged
AbdallahS merged 2 commits intoas/myclormfrom
253-the-recoverable-operator-mechanism-is-buggy
Apr 21, 2026
Merged

253 the recoverable operator mechanism is buggy#256
AbdallahS merged 2 commits intoas/myclormfrom
253-the-recoverable-operator-mechanism-is-buggy

Conversation

@VictosVertex
Copy link
Copy Markdown
Collaborator

@VictosVertex VictosVertex commented Apr 21, 2026

This fixes #253 by disabling computeIdx if the operation is known to be bad.

@AbdallahS AbdallahS merged commit 160f2f2 into as/myclorm Apr 21, 2026
@AbdallahS AbdallahS deleted the 253-the-recoverable-operator-mechanism-is-buggy branch April 21, 2026 22:55
AbdallahS pushed a commit that referenced this pull request Apr 22, 2026
* known to be bad operations disable computeIdx

* formatting
AbdallahS added a commit that referenced this pull request Apr 23, 2026
* mini clean-up of myclorm

* myclorm: remove some legacy code and add unit tests

* fixing some myclorm edge cases

* Propagator: use ref for sets instead of val/ref

* early access positive wellformedness

* syntax error detection for variables, sets, and multimaps.

* Add unit test for equality with bad

* Add unit test for equivalence with bad.

* execution_declare to always define its output variables

* 253 the recoverable operator mechanism is buggy (#256)

* known to be bad operations disable computeIdx

* formatting

* Add python expressions.

* Fix #251

* Fix #255

* Clean up a bit and deprecate assign/3

* share implementation of ensure and evaluate between the compile and ground engines

* share some implementation of executions between the compile and ground engines

* Share execution fail between compile and ground

* Avoid a loop in sets that leads to problems similar to #255

* Rework variadic operator type handling, to be static and a bit faster.

* Remove usc active for now.

* restore accidentally changed parameter

* Use shorter performance targets in benchmarks.

* Strange performance behaviour.

---------

Co-authored-by: VictosVertex <Victos.Vertex@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants