You /are/ actually passing in a second argument though, your second
argument is `undefined`. Default arguments aren't meant to replace
`undefined` values, they're meant to be permissible for omission.
--
Keith Cirkel
On 10 October 2012 14:19, David Bruant bruan...@gmail.com wrote:
Hi,
I've
Is it worth pointing out that RFC3339[1] exists to specify a stricter
standard than ISO8601?
[1]: http://www.ietf.org/rfc/rfc3339.txt
--
Keith Cirkel
On 29 April 2013 19:10, Jason Orendorff jason.orendo...@gmail.com wrote:
On Sun, Apr 28, 2013 at 9:36 AM, Allen Wirfs-Brock
al...@wirfs
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
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
Hello all!
While I am aware that previous proposals for operator overloading exist, I
thought I'd attempt to write one which I consider to be simpler and more
extensible - utilising Symbols.
https://github.com/keithamus/ecmascript-operator-overloading-proposal
It'd be great to get some feedback
As functional programming because more mainstream - developers are leaning
more and more on immutability - with tools like immutable.js. However there
exists perfectly good solutions inside of JS with Object.seal &
Object.freeze.
I propose making a short syntax to allow for creating of
6 matches
Mail list logo