On 27/03/17 16:06, Andrey Breslav wrote:
- I can check for (a != null) and then somewhere inside check for (a is MyClass). This does not directly apply to Java (unless we envision introduction of nullable types in the future). - In a mixed hierarchy, it may often makes sense to first check for (a is CharSequence) and later — for (a is List), having methods of both CharSequence and List on a. I can look for exact examples, if they are of interest to you
Thanks - that answer my question :-) Maurizio
