Michel Hermier

This change is problematic in another way, it introduce friction with the setter syntax, in many ways. Which of the following is legal/looks the correct answer ? ```javascript /* 1...

> Should argument labels be part of the method signature? (That is different labels, different method.) Yes, otherwise is as useful as a glorified comment, and brings not much value....

It is implementation details, and as this it does not solve calling conventions...

I mean it is implementation detail, because what you propose is a syntax sugar to avoid parameter duplication. The main issue is how labels should be treated and distinguished at...

I don't know why the string is `strip`ed here, but it doesn't seems the sensible way to do. Instead, a `strip` method should be provided instead and let the user...

The statement "C itself which saves you having to trim off extraneous characters after the numerical part" is misleading. The libc API offers incremental parsing. As such it is up...

@PureFox48 I'm not against it, but if an API is complex and user can fall into a pit of partial success by being lazy, they will do. The problem with...

Anyway, I think the way it is fixed here is acceptable.

`List.filled(_,_)` as 2 side effect that this patch does not have. It does provides an internal buffer and `List` of the exact size. Even adding a `removeAll()` would be me...

I would say no to that addition. We already have `sequenceable[index]` and `sequenceable.where(unaryPredicate)[index]` with index 0 and -1 to achieve the same results. Also if `first` was added, what about...