determin1st

im just encountered, that i never used `for own` because i never used prototyped objects in the `for` loop, always plain objects, so had no collisions so far..

what about this syntax: ```livescript a own 'defaultProp' ``` to: ``` a.hasOwnProperty('defaultProp'); ```

Some speed test for `in` operator vs `hasOwnProperty()`: https://andrew.hedges.name/experiments/in/ In my browsers Firefox v61, Chrome v64, the function hasOwnProperty always runs faster with 1.000.000 elements. I came to that test...

well, i've created 4000 DOM elements and constructed my objects above them using options parser (it took 200ms - inacceptable for smooth interaction with user - for example mouse hover...

It's for testing only. Wanna me drop a link? Sometimes you need to animate several elements at once. For example some rain of particles which follow the mouse move or...

https://jsperf.com/object-spread-vs-polyfill/1

hey, what about a little optimization for the `import$` function? is it really needed to do `var own = {}.hasOwnProperty;` assignment before the cycle?

@pepkin88 `Object.assign` is slower than `import$$` in that test, why do you choice it? Im not quite clear about "fallback implementation" you mentioned, what is that?

@pepkin88 okay, checkout another `import$$$` variant: https://jsperf.com/object-spread-vs-polyfill How do livescript detect that there is no `Object.assign`? at runtime? hmm.. i've checked, yes. Is it really hard to make all things...

summivox, Yes, this does the job, but the topic is not really about the job.