On 2015/03/06 13:52:13, caitp wrote:
The error is that the `prototype` property is set up with writable=false,
configurable=false properties --- so the expected error is either
`strict_cannot_assign` or `strict_read_only_property`, and shouldn't
affect
sloppy mode once the construct is available in sloppy mode.
I think this could be fixed just by making sure that when defining class
properties, property attributes are not ignored.
Yes. That was my first thought too. But since the only non configurable own
property is the prototype property there is no need to check the common
cases on
non computed, non static properties.
https://codereview.chromium.org/985643003/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
