#50 reflective: recursive interface tree

已關閉
ranides4 年之前創建 · 2 條評論

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 評論 3 年之前'
所有者

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 評論 3 年之前'
所有者

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

Depends on: #98 **Write IteratorUtils.flatIf and better CQuery.flatIf**
ranides3 年之前 關閉
ranides 在代碼提交 3 年之前 中引用了該問題
登入 才能加入這對話。
未選擇里程碑
未指派成員
1 參與者
正在加載...
取消
保存
尚未有任何內容