2015-03-16 17:53 GMT+01:00 Allen Wirfs-Brock al...@wirfs-brock.com:
It's possible, that in the future derived reflective operations such as
those might be added to Reflect.*.
There are a couple of design questions to consider for future extensions:
1) Is there any benefit to duplicating to
Thanks Allen and Jason! This completely cleared it all up for me!
On 16 March 2015 at 18:15, Jason Orendorff jason.orendo...@gmail.com
wrote:
On Mon, Mar 16, 2015 at 11:53 AM, Allen Wirfs-Brock
al...@wirfs-brock.com wrote:
In ES6, the primary role of the Reflect object is to provide direct
On Mar 15, 2015, at 2:48 PM, Keith Cirkel wrote:
It seems like the intention of the Reflect API was to create a standard
object were all reflection operations could reside.
Now that we have modules, a “@reflect” module is a more natural place for
many of the reflection methods previously
On Mon, Mar 16, 2015 at 11:53 AM, Allen Wirfs-Brock
al...@wirfs-brock.com wrote:
In ES6, the primary role of the Reflect object is to provide direct access
to an object's essential internal methods:
It seems like the intention of the Reflect API was to create a standard
object were all reflection operations could reside.
Now that we have modules, a “@reflect” module is a more natural place for
many of the reflection methods previously defined on Object. For
backwards-compatibility
5 matches
Mail list logo
