Bug in lazy cp atoms
Issue #654
open
No description provided.
Comments (6)
-
-
- changed status to resolved
Fixes #654: out of bounds was not checked in lazy cp grounder.
→ <<cset 606517e41c80>>
-
Added unit test for refs #654.
→ <<cset f576c3eccd19>>
-
reporter
Revert "Fixes #654: out of bounds was not checked in lazy cp grounder."
This reverts commit 606517e41c803008fe3a69e89c469847cc136fdc.
→ <<cset 068d3814d9e0>>
-
reporter
- changed status to open
The proposed fix (commit 606517e) introduces a lot of extra bugs.
I reverted this fix (I should never have accepted it)
Hence...
-
reporter
faulty fix on branch cpfix_faulty
- Log in to comment
The problem is caused by the fact that code is organized such that types are not checked during translation but should done before (as in atomgrounder), but the lazy grounders don't do this atm.