great, I was expecting an announcement here.
On Wed, Apr 20, 2016 at 1:45 PM, Michael Ficarra wrote:
> The notes have already been posted at
> https://github.com/tc39/tc39-notes/tree/4d5fb147e6b714f682aaf5da803ca14ec5fb3b82/es7/2016-03
> .
>
> On Wed, Apr 20, 2016
On Sat, Apr 16, 2016 at 7:53 AM, Caitlin Potter wrote:
> How would that interact with angular.js' Function.prototype.toString
> parsing? Seems like doing that could break some content, even if it were
> useful
>
Comments are generally a failure of the developer to write
Perhaps this proposal might fit with what you had in mind:
https://esdiscuss.org/topic/proposal-for-a-null-coalescing-operator
Been meaning to clean this up and submit it as an actual proposal since the
idea is kind of simple:
https://github.com/sirisian/ecmascript-null-coalescing-operator
The notes have already been posted at
https://github.com/tc39/tc39-notes/tree/4d5fb147e6b714f682aaf5da803ca14ec5fb3b82/es7/2016-03
.
On Wed, Apr 20, 2016 at 7:45 AM, John Lenz wrote:
> Any update on this?
>
> On Wed, Apr 6, 2016 at 4:25 PM, Rick Waldron
Any update on this?
On Wed, Apr 6, 2016 at 4:25 PM, Rick Waldron wrote:
> Where are they? I haven't seen anyone post them for approval.
>
> On Tue, Apr 5, 2016 at 8:39 PM Jordan Harband wrote:
>
>> The notes were taken, but have not yet been approved
My initial motivation was to create a Python-style help() function. But I agree
that it’s probably better not to depend on this mechanism.
> On 16 Apr 2016, at 19:28, Jordan Harband wrote:
>
> As I see it, the primary purpose of the `Function#toString` proposal is to
>
Right. That’s a compelling argument against my suggestion.
> On 16 Apr 2016, at 16:53, Caitlin Potter wrote:
>
> How would that interact with angular.js' Function.prototype.toString parsing?
> Seems like doing that could break some content, even if it were useful
>
>
7 matches
Mail list logo