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

Issue 27619002: Check that class member names do not conflict with type parameters (Closed)

Created:
7 years, 2 months ago by hausner
Modified:
7 years, 2 months ago
Reviewers:
srdjan
CC:
reviews_dartlang.org, vm-dev_dartlang.org, kasperl
Visibility:
Public.

Description

Check that class member names do not conflict with type parameters Implement check that member names do not conflict with type parameters. Simplify name checks in class namespace. Mark typevariable_mirror_metadata_test as failing now that we report the proper compile time errors. (The test expects no errors.) Some co19 tests expect a name conflict between a setter X= and type parameter X. This is still in flux from a language perspective. This change list does not introduce an compile error for this case. Fix for issue 13701. R=srdjan@google.com Committed: https://code.google.com/p/dart/source/detail?r=28808

Patch Set 1 #

Patch Set 2 : #

Total comments: 7

Patch Set 3 : #

Patch Set 4 : #

Patch Set 5 : #

Unified diffs Side-by-side diffs Delta from patch set Stats (+82 lines, -144 lines) Patch
M runtime/vm/parser.h View 1 2 1 chunk +1 line, -0 lines 0 comments Download
M runtime/vm/parser.cc View 1 2 3 14 chunks +64 lines, -129 lines 0 comments Download
M tests/co19/co19-co19.status View 1 2 1 chunk +3 lines, -9 lines 0 comments Download
M tests/co19/co19-dart2dart.status View 1 2 1 chunk +7 lines, -0 lines 0 comments Download
M tests/co19/co19-dart2js.status View 1 2 1 chunk +6 lines, -0 lines 0 comments Download
M tests/language/language.status View 1 2 1 chunk +0 lines, -6 lines 0 comments Download
M tests/lib/lib.status View 1 2 1 chunk +1 line, -0 lines 0 comments Download

Messages

Total messages: 5 (0 generated)
hausner
7 years, 2 months ago (2013-10-17 00:28:51 UTC) #1
srdjan
lgtm https://codereview.chromium.org/27619002/diff/7001/runtime/vm/parser.cc File runtime/vm/parser.cc (right): https://codereview.chromium.org/27619002/diff/7001/runtime/vm/parser.cc#newcode554 runtime/vm/parser.cc:554: const char* Kind() const { I would expect ...
7 years, 2 months ago (2013-10-17 17:26:27 UTC) #2
hausner
https://codereview.chromium.org/27619002/diff/7001/runtime/vm/parser.cc File runtime/vm/parser.cc (right): https://codereview.chromium.org/27619002/diff/7001/runtime/vm/parser.cc#newcode554 runtime/vm/parser.cc:554: const char* Kind() const { On 2013/10/17 17:26:27, srdjan ...
7 years, 2 months ago (2013-10-17 17:39:03 UTC) #3
hausner
Committed patchset #5 manually as r28808 (presubmit successful).
7 years, 2 months ago (2013-10-17 17:39:17 UTC) #4
srdjan
7 years, 2 months ago (2013-10-17 17:48:13 UTC) #5
Message was sent while issue was closed.
https://codereview.chromium.org/27619002/diff/7001/runtime/vm/parser.cc
File runtime/vm/parser.cc (right):

https://codereview.chromium.org/27619002/diff/7001/runtime/vm/parser.cc#newco...
runtime/vm/parser.cc:3247: Field& class_field = Field::Handle();
On 2013/10/17 17:39:03, hausner wrote:
> On 2013/10/17 17:26:27, srdjan wrote:
> > s/Handle/ZoneHandle/ as it escapes scope via field->field_.
> 
> It has escaped before, too, into the list of fields in 'members'. Did we just
> get lucky?
> 
> Done

Right now we do not set up HandleScopes eagerly, but they have a large scope
(whole parser or more).

Powered by Google App Engine
This is Rietveld 408576698