[[Set]] and inherited readonly data properties

Andrea Giammarchi andrea.giammarchi at gmail.com
Mon Mar 31 08:56:16 PDT 2014

It's in the latest node v8 and i thought it was a hack introduced on
purpose as mentioned before, apparently it's not, but still around.

Sent from my Windows Phone From: Andreas Rossberg
Sent: 3/31/2014 5:33
To: Andrea Giammarchi
Cc: Brendan Eich; es-discuss
Subject: Re: [[Set]] and inherited readonly data properties
On 28 March 2014 23:00, Andrea Giammarchi <andrea.giammarchi at gmail.com> wrote:
> For the sake of examples, I honestly find current V8 hack, tested in node.js
> inconsistent, kinda pointless, and quite disturbing, with or without strict
> code.

I don't know what your notion of "current" is, but this bug has been
fixed long ago. And being pointless is the nature of bugs.

> Why JavaScript engines need so much fragmentation with these kind of
> unspeced behavior ... this, as a developer, I've never got it.

Just to annoy developers, of course. It's got nothing to do with the
byzantine complexity of the language.


More information about the es-discuss mailing list