If I see string.chars I expect to see a bucket of char, and not the count of chars. That name needs to be more explicit.
If I see string.chars I expect to see a bucket of char, and not the count of chars. That name needs to be more explicit.
Perl 6 is not softly typed, it's gradually typed. It's as hard as you want to make it.
> If I see string.chars I expect to see a bucket of char
Why? Is that an expectation that comes from some other language? There's only so much you can expect a language to follow the semantics of other languages. Perl 6 will have it's own quirks, expecting it to conform to some malleable standard based on what some percentage of other languages do is not something I think is entirely fair to expect.
No, the convention that (thing that can be viewed as a collection of subelements in several different ways).(plural name for one kind of subelement) is a property/method providing a collection of the subelements of the named type is not only common in other languages, it is also quite common in Perl 6 -- and even followed (aside from chars) in the Str class specifically; examples include (from Str): univals, lines, words, ords
chars is the odd man out here: charcount or something similar would have been a lot cleaner. (Yes, its consistent with elems, but that seems to be poorly chosen for the same reason; its a plural name, but it provides a single numeric value.)
It seems this and a lot of other details were intentionally made to clash with our habits, as I write in my other comment.
I can see that, and I don't think its all that bad, just suboptimal, and confusing based on more than just expectations shaped by other languages.
<noun>s always has denoted some sort of collection to me and I'm sure you'll see many people have the same confusion.