Hi Joe,
I don't understand what|CircularDep|and|NonCircularDep|refer to. To me,
all the modules in the question contain some form of circular
dependencies. Can you please post an answer in terms of|A|,|B|,|C|as
defined in http://stackoverflow.com/q/38841469/14731 ?
Thank you,
Gili
__
On 28/05/2014 2:59 PM, Tab Atkins Jr. wrote:
On Wed, May 28, 2014 at 11:51 AM, cowwoc wrote:
Wow, what a mess. I've been pretty methodical about semicolons in my code so
I forgot about this "feature" :)
I'm not a fan of ASI, but in light of your example I agree there is
a
On 28/05/2014 2:43 PM, Oliver Hunt wrote:
On May 28, 2014, at 11:39 AM, cowwoc wrote:
Don't we use a semicolon to denote the end of an expression context? Perhaps
I'm missing something, but I see no ambiguity in the example you gave. I expect:
return {};
and
return
On 28/05/2014 2:42 PM, Brendan Eich wrote:
Oliver Hunt wrote:
What you're asking for is grammatically ambiguous in a way that would
potentially break existing content, and (generally) leads to really
interesting parsing behaviour.
As Doug Crockford has argued, this is why K&R style is better
On 28/05/2014 2:33 PM, Oliver Hunt wrote:
On May 28, 2014, at 11:23 AM, cowwoc <mailto:cow...@bbs.darktech.org>> wrote:
if (foo)
return
{
L: print(something)
}
The only way to disambiguate this in the general case is to have a rule
such as
to allow us to be sure that the opening
Oliver Hunt-2 wrote
>> On May 28, 2014, at 11:10 AM, cowwoc <
> cowwoc@.darktech
> > wrote:
>>
>> I would like the specification to also allow the following syntax:
>>
>> return
>> {
>> key: "value"
>> };
>
> Th
Hi,
Please let me know whether I've got the right mailing list.
I'd like to propose a change to ECMAScript. Right now the following syntax
is required for returning an anonymous object:
return {
key: "value"
};
I would like the specification to also allow the following syntax:
return
7 matches
Mail list logo
