44d3b8fb1a
ExpressionsOfTypeProcessor searches for all occurence of expression with given type. It start from usages of the class, searches for sub-classes, declarations that return those classes, usages of these declarations, and so on. During this search, find usages for all operators that return the subject type is executed as sub-queries. Full search for such queries can't give addition types. And it also shouldn't give additional scopes for search, because same scopes should be located by operands. In other words, if sub-query can spot the scope of usage starting from the same type, the original query should also process same scope. #KT-18566 Fixed
9 lines
320 B
Plaintext
Vendored
9 lines
320 B
Plaintext
Vendored
Checked type of u1
|
|
Checked type of u2
|
|
ExpressionOfTypeProcessor is already started for UnaryNot. Exit for operator UnaryNot.not().
|
|
Resolved !u1
|
|
Searched references to UnaryNot
|
|
Searched references to UnaryNot.not() in non-Java files
|
|
Searched references to u1 in non-Java files
|
|
Searched references to u2 in non-Java files
|