for own(...) loop (spin-off from Re: for..in, hasOwnProperty(), and inheritance)

[Felipe Gasper]

On 11/8/11 2:49 PM, Brendan Eich wrote:
>
> Should ES.next provide sugar for the recommended pattern? To make it
> compose with declarations and destructuring in the for head, it should
> use a contextual keyword immediately after 'for':
>
> for own (i in o) {
> /body/
> }
>
> This is a small thing but it might pay off in the long run.

This is a fantastic idea, IMO.

The hasOwnProperty() thing is buggy if you create a “hasOwnProperty” 
property on the object, and it’s wordy besides.

-FG