--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMd%2BM7w_4-eJufKNB3gBzj2EsZUng0VD%3DmzbPmBr7q_-zn-yFw%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
--
--
v8-users mailing list
v8-u...@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups "v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
As exciting as this is, can anyone please explain why a feature called "public field" is being announced with properties prefixed by an underscore, which historically means "protected" or, to some extend, private property, in JavaScript-land ?This is a question specially for those that might decide to write some blog-post about this new feature: please don't use `_counter` or, if you like that, please explain that using `_` is just an author convention and it has nothing to do with the public field proposal itself.Thanks for your understating and for considering a better divulgation of such welcome news.Best Regards
--
--
v8-dev mailing list
v8-...@googlegroups.com
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 v8-dev+un...@googlegroups.com.