#50 reflective: recursive interface tree

Zamknięty
otworzone 4 lat temu przez ranides · 2 komentarzy
ranides skomentował 4 lat temu

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 skomentował 3 lat temu
Właściciel

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 skomentował 3 lat temu
Właściciel

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

Depends on: #98 **Write IteratorUtils.flatIf and better CQuery.flatIf**
ranides wspomina ten problem w commicie 3 lat temu
Zaloguj się, aby dołączyć do tej rozmowy.
Brak kamienia milowego
Brak przypisania
1 uczestników
Ładowanie...
Anuluj
Zapisz
Nie ma jeszcze treści.