#50 reflective: recursive interface tree

Geschlossen
vor 4 Jahren geöffnet von ranides · 2 Kommentare
ranides kommentierte vor 4 Jahren

At this moment, #interfaces returns interfaces directly implemented by this class. Or interfaces directly implemented by this and all parent classes.

The problem is, that we do not return transitive interfaces.

For example, if we implemented List, then there is no way ti find out, that we implemented Collection too.

At this moment, `#interfaces` returns interfaces directly implemented by this class. Or interfaces directly implemented by this and all parent classes. The problem is, that we do not return transitive interfaces. For example, if we implemented `List`, then there is no way ti find out, that we implemented `Collection` too.
ranides kommentierte vor 3 Jahren
Besitzer

Complexity probably comes from the fact that we don't want to return duplicates (can be done effectively by CQuery.distinct) AND we need to resolve recursively at the same time.

We don't have anything like recursive CQuery.flatIf. We should have, to be honest. Maybe task can be solved easily by implementing something like that.

Todo recurvise flatten, named CQuery.flatWhile

Complexity probably comes from the fact that we don't want to return duplicates (can be done effectively by CQuery.distinct) AND we need to resolve recursively at the same time. We don't have anything like recursive CQuery.flatIf. We should have, to be honest. Maybe task can be solved easily by implementing something like that. Todo recurvise flatten, named `CQuery.flatWhile`
ranides kommentierte vor 3 Jahren
Besitzer

Depends on: #98 Write IteratorUtils.flatIf and better CQuery.flatIf

Depends on: #98 **Write IteratorUtils.flatIf and better CQuery.flatIf**
ranides hat vor 3 Jahren geschlossen
ranides hat dieses Issue vor 3 Jahren aus einem Commit referenziert
Anmelden, um an der Diskussion teilzunehmen.
Kein Meilenstein
Niemand zuständig
1 Beteiligte
Laden…
Abbrechen
Speichern
Hier gibt es bis jetzt noch keinen Inhalt.