<@U092N7GGG>: Thanks for the explanation.
In the c...
# announcementse
eric.kolotyluk
02/02/2016, 9:17 PM@yole: Thanks for the explanation.
In the case of Path, it is not a list, but I appreciate that Kotlin treats it like a collection because it inherits from Iterable. I don't really have a problem with that decision, but it does lead to confusion because of the ambiguity involved. The problem with ambiguous situations is the the decision the compiler makes may not be the one the developer had in mind. It would be nice if the compiler issued a warning, and the IDE offered the various choices in the ambiguous decision.