Ticket #47 (new defect)
Handle derived index errors caused by missing slots in a redefined class
| Reported by: | ieslick | Owned by: | ieslick |
|---|---|---|---|
| Priority: | major | Milestone: | Release 1.0 beta 1 - Schemas, advanced indexing, postmodern |
| Component: | metaprotocol | Version: | |
| Keywords: | Cc: |
Description
Derived indices depend on a class instance for their value. This usually means they perform some computation over slot values. What happens when a slot is removed, but the index is not? Today it will provide a nonsensical error message about a non-applicable generic function.
- We can ensure that the dependencies of a derived index are maintained explicitly so the deletion happens automatically (see - We can provide a sensible error message with restart options that removes the failing derived index
This should be tied up in a ticket to only update derived indexes when slots they depend on are updated.
My plan is: support hints, do auto updates when hints indicate a lost dependency, otherwise provide an interactive, restartable error to remove the derived index.
