#50 reflective: recursive interface tree

Ditutup
dibuka 4 tahun lalu oleh ranides · 2 komentar

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 komentar 3 tahun lalu
Pemilik

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 komentar 3 tahun lalu
Pemilik

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

Depends on: #98 **Write IteratorUtils.flatIf and better CQuery.flatIf**
ranides referenced this issue from a commit 3 tahun lalu
Masuk untuk bergabung dalam percakapan ini.
Tidak ada tonggak
Tidak ada penerima
1 Peserta
Memuat...
Batal
Simpan
Belum ada konten.