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

Issue 11419191: Enforce rule in vm that factory name must match enclosing class name. (Closed)

Created:
8 years ago by regis
Modified:
8 years ago
Reviewers:
hausner
CC:
reviews_dartlang.org
Visibility:
Public.

Description

Enforce rule in vm that factory name must match enclosing class name. This is a step towards removing support for obsolete default factory classes. For now, disable tests using obsolete syntax. More will get disabled as support is completely removed. We may then permanently remove some tests, while updating and reenabling others whose purpose is not related to default factory classes. Committed: https://code.google.com/p/dart/source/detail?r=15428

Patch Set 1 #

Total comments: 6

Patch Set 2 : #

Unified diffs Side-by-side diffs Delta from patch set Stats (+72 lines, -32 lines) Patch
M runtime/lib/error.dart View 1 1 chunk +1 line, -1 line 0 comments Download
M runtime/lib/map_patch.dart View 1 1 chunk +1 line, -1 line 0 comments Download
M runtime/tests/vm/vm.status View 1 1 chunk +1 line, -0 lines 0 comments Download
M runtime/vm/parser.cc View 1 2 chunks +15 lines, -26 lines 0 comments Download
M runtime/vm/symbols.h View 1 1 chunk +1 line, -1 line 0 comments Download
M tests/co19/co19-runtime.status View 1 1 chunk +2 lines, -3 lines 0 comments Download
M tests/language/language.status View 1 1 chunk +51 lines, -0 lines 0 comments Download

Messages

Total messages: 3 (0 generated)
regis
8 years ago (2012-11-27 23:13:22 UTC) #1
hausner
LGTM with question. https://codereview.chromium.org/11419191/diff/1/runtime/vm/parser.cc File runtime/vm/parser.cc (right): https://codereview.chromium.org/11419191/diff/1/runtime/vm/parser.cc#newcode2982 runtime/vm/parser.cc:2982: ParseQualIdent(&factory_name); Does it still make sense ...
8 years ago (2012-11-28 00:26:38 UTC) #2
regis
8 years ago (2012-11-28 01:09:18 UTC) #3
Thanks!

https://codereview.chromium.org/11419191/diff/1/runtime/vm/parser.cc
File runtime/vm/parser.cc (right):

https://codereview.chromium.org/11419191/diff/1/runtime/vm/parser.cc#newcode2982
runtime/vm/parser.cc:2982: ParseQualIdent(&factory_name);
On 2012/11/28 00:26:38, hausner wrote:
> Does it still make sense to use ParseQualIdent now that the factory name must
> match the class name? Essentially we can now at most have one period in the
> name, and the first identifier we read must match the class name. What am I
> missing?

You are right. I simplified this code further.

https://codereview.chromium.org/11419191/diff/1/tests/language/language.status
File tests/language/language.status (right):

https://codereview.chromium.org/11419191/diff/1/tests/language/language.statu...
tests/language/language.status:82: [ $compiler == none && $unchecked ]
On 2012/11/28 00:26:38, hausner wrote:
> Add a blank line before the new section?

I skipped the blank line to group these failures under "test issue 6324". But I
can repeat the comment with a blank line. Done.

https://codereview.chromium.org/11419191/diff/1/tests/language/language.statu...
tests/language/language.status:94: [ $compiler == none && $checked ]
On 2012/11/28 00:26:38, hausner wrote:
> Add a blank line before the new section?
ditto

Powered by Google App Engine
This is Rietveld 408576698