Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(117)

Issue 9581032: New test exposes some bugs in the static analysis (dartc) engine on assignment problems (Closed)

Created:
8 years, 9 months ago by zundel
Modified:
8 years, 9 months ago
Reviewers:
gbracha
CC:
reviews_dartlang.org, rdayal_google.com, danrubel
Visibility:
Public.

Description

New test exposes some bugs in the static analysis (dartc) engine on assignment problems http://code.google.com/p/dart/issues/detail?id=1957 Committed: https://code.google.com/p/dart/source/detail?r=4963

Patch Set 1 : new test for static analysis. #

Total comments: 2
Unified diffs Side-by-side diffs Delta from patch set Stats (+37 lines, -0 lines) Patch
M tests/language/language.status View 1 chunk +4 lines, -0 lines 0 comments Download
A tests/language/src/AssignStaticTypeTest.dart View 1 chunk +33 lines, -0 lines 2 comments Download

Messages

Total messages: 3 (0 generated)
zundel
8 years, 9 months ago (2012-03-02 23:58:22 UTC) #1
gbracha
lgtm with comments http://codereview.chromium.org/9581032/diff/4/tests/language/src/AssignStaticTypeTest.dart File tests/language/src/AssignStaticTypeTest.dart (right): http://codereview.chromium.org/9581032/diff/4/tests/language/src/AssignStaticTypeTest.dart#newcode9 tests/language/src/AssignStaticTypeTest.dart:9: int a = "String"; /// 01: ...
8 years, 9 months ago (2012-03-05 16:51:08 UTC) #2
zundel
8 years, 9 months ago (2012-03-05 17:37:48 UTC) #3
http://codereview.chromium.org/9581032/diff/4/tests/language/src/AssignStatic...
File tests/language/src/AssignStaticTypeTest.dart (right):

http://codereview.chromium.org/9581032/diff/4/tests/language/src/AssignStatic...
tests/language/src/AssignStaticTypeTest.dart:9: int a = "String";  /// 01:
static type error
On 2012/03/05 16:51:08, gbracha wrote:
> Could we change all the comments 01 -06 in class A to say "static type
warning"
> instead of static type error? I'd like to firmly entrench the correct
> terminology to avoid confusion.

I agree it has caused lots of confusion. I will make a CL to do this (which will
touch a lot of files)

Powered by Google App Engine
This is Rietveld 408576698