It's visually ambiguous, though. I really don't want to be reading `foo..bar()` and `1..toString()` in the same file. They look the same, but mean two completely different things.
In a language that has this feature, I almost never use it, anyways, unless I'm interacting with the DOM. And even then, I'm not saving that much typing. Not with an editor with tab completion (most do). On Thu, Oct 29, 2015, 19:29 Claude Pache <[email protected]> wrote: > > > > Le 30 oct. 2015 à 00:07, Waldemar Horwat <[email protected]> a écrit : > > > >> On 10/29/2015 14:20, Claude Pache wrote: > > > >> In some cases – as in `3..toStrign()` –, `undefined` will be produced > where an error was thrown. > > > > > > No, this would continue to throw an error. > > Oops, you're right. So, `..` is 100% backward-compatible. > > —Claude > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
