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

Issue 11232071: Ambiguous references do not necessarily cause compilation errors (issue 5736). (Closed)

Created:
8 years, 2 months ago by regis
Modified:
8 years, 2 months ago
Reviewers:
hausner, Ivan Posva
CC:
reviews_dartlang.org
Visibility:
Public.

Description

Ambiguous references do not necessarily cause compilation errors (issue 5736). Triage related co19 test failures. Committed: https://code.google.com/p/dart/source/detail?r=13987

Patch Set 1 #

Total comments: 5
Unified diffs Side-by-side diffs Delta from patch set Stats (+182 lines, -68 lines) Patch
M runtime/vm/class_finalizer.h View 1 chunk +7 lines, -4 lines 0 comments Download
M runtime/vm/class_finalizer.cc View 6 chunks +23 lines, -6 lines 0 comments Download
M runtime/vm/parser.h View 2 chunks +16 lines, -7 lines 0 comments Download
M runtime/vm/parser.cc View 14 chunks +114 lines, -38 lines 2 comments Download
M tests/co19/co19-runtime.status View 3 chunks +22 lines, -13 lines 3 comments Download

Messages

Total messages: 6 (0 generated)
regis
8 years, 2 months ago (2012-10-23 21:28:43 UTC) #1
hausner
lgtm https://codereview.chromium.org/11232071/diff/1/runtime/vm/parser.cc File runtime/vm/parser.cc (right): https://codereview.chromium.org/11232071/diff/1/runtime/vm/parser.cc#newcode7665 runtime/vm/parser.cc:7665: // malformed if type arguments have previously been ...
8 years, 2 months ago (2012-10-23 22:02:24 UTC) #2
regis
Thanks! https://codereview.chromium.org/11232071/diff/1/runtime/vm/parser.cc File runtime/vm/parser.cc (right): https://codereview.chromium.org/11232071/diff/1/runtime/vm/parser.cc#newcode7665 runtime/vm/parser.cc:7665: // malformed if type arguments have previously been ...
8 years, 2 months ago (2012-10-23 22:30:25 UTC) #3
Ivan Posva
https://codereview.chromium.org/11232071/diff/1/tests/co19/co19-runtime.status File tests/co19/co19-runtime.status (right): https://codereview.chromium.org/11232071/diff/1/tests/co19/co19-runtime.status#newcode5 tests/co19/co19-runtime.status:5: # These tests need to be updated for new ...
8 years, 2 months ago (2012-10-24 05:47:52 UTC) #4
regis
https://codereview.chromium.org/11232071/diff/1/tests/co19/co19-runtime.status File tests/co19/co19-runtime.status (right): https://codereview.chromium.org/11232071/diff/1/tests/co19/co19-runtime.status#newcode5 tests/co19/co19-runtime.status:5: # These tests need to be updated for new ...
8 years, 2 months ago (2012-10-24 16:50:31 UTC) #5
Ivan Posva
8 years, 2 months ago (2012-10-24 17:20:09 UTC) #6
https://codereview.chromium.org/11232071/diff/1/tests/co19/co19-runtime.status
File tests/co19/co19-runtime.status (right):

https://codereview.chromium.org/11232071/diff/1/tests/co19/co19-runtime.statu...
tests/co19/co19-runtime.status:5: # These tests need to be updated for new
optional parameter syntax and semantics, co19 issue 258:
On 2012/10/24 16:50:32, regis wrote:
> On 2012/10/24 05:47:53, Ivan Posva wrote:
> > Why did this line move? It should be unrelated to this current change.
> 
> A new group of failing tests is introduced on line 12. These tests relate to
> co19 issue 282, but some fail in production mode, some in checked mode. The
> filters are therefore inside the group, i.e. after the comment header.
> This group for co19 issue 258 had the filter before the comment header. This
> could be a problem if you move the group somewhere and forget to move the
> filter. 

Thanks for the clarification.

Powered by Google App Engine
This is Rietveld 408576698