Grokkers that subclass other Grokkers

Bug #92232 reported by Jan Wijbrand Kolman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grok
Won't Fix
Low
Martijn Faassen
1.1
Confirmed
Undecided
Unassigned

Bug Description

We have a Grokker B which subclasses from Grokker A. We need to use priorities to make sure B actually groks its components instead of A. If the priorities are equal, which Grokker is being used is not deterministic.

This can lead to code that sometimes works but stops working later.

We need a way to detect this situation and when it happens bail out with a GrokError.

Revision history for this message
Jan Wijbrand Kolman (janwijbrand) wrote :

Martijn just notes: we need to think about sibbling subclasses from A.

todd (todd-infrae)
Changed in grok:
assignee: nobody → faassen
milestone: none → 1.0
Revision history for this message
Martijn Faassen (faassen) wrote :

This isn't a very important issue, so I'm going to defer this to the future.

Changed in grok:
importance: Undecided → Low
milestone: 1.0 → 1.1
Changed in grok:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.