Improve a reason for failure.

Improve a reason for failure.

TBR=smok@google.com

Committed: https://code.google.com/p/dart/source/detail?r=10729

[Roman, 2012-08-15 14:00:45]

lgtm

https://chromiumcodereview.appspot.com/10823343/diff/1/tests/language/languag...
File tests/language/language.status (left):

https://chromiumcodereview.appspot.com/10823343/diff/1/tests/language/languag...
tests/language/language.status:227: syntax_test/47: Fail  # We should get
compile-time error on const constructor having body. But we don't emit default
constructors with empty body.
Actually we can fix this failure reason if we emit empty constructors. So that's
probably dart2dart fault, not dart2js

[Anton Muhin, 2012-08-15 14:02:28]

https://chromiumcodereview.appspot.com/10823343/diff/1/tests/language/languag...
File tests/language/language.status (left):

https://chromiumcodereview.appspot.com/10823343/diff/1/tests/language/languag...
tests/language/language.status:227: syntax_test/47: Fail  # We should get
compile-time error on const constructor having body. But we don't emit default
constructors with empty body.
I thought about that be decided against: it's apparently compile-time error to
see const A() {}, so it should be treated in parser/resolver, not in dart
backend.

Thoughts?

On 2012/08/15 14:00:45, Roman wrote:
> Actually we can fix this failure reason if we emit empty constructors. So
that's
> probably dart2dart fault, not dart2js

[Roman, 2012-08-15 14:13:35]

lgtm

https://chromiumcodereview.appspot.com/10823343/diff/1/tests/language/languag...
File tests/language/language.status (left):

https://chromiumcodereview.appspot.com/10823343/diff/1/tests/language/languag...
tests/language/language.status:227: syntax_test/47: Fail  # We should get
compile-time error on const constructor having body. But we don't emit default
constructors with empty body.
On 2012/08/15 14:02:28, Anton Muhin wrote:
> I thought about that be decided against: it's apparently compile-time error to
> see const A() {}, so it should be treated in parser/resolver, not in dart
> backend.
> 
> Thoughts?
> 
> On 2012/08/15 14:00:45, Roman wrote:
> > Actually we can fix this failure reason if we emit empty constructors. So
> that's
> > probably dart2dart fault, not dart2js
> 

Agreed that it should be compiler-time error.