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

Issue 11117022: Fix a crash related to obsolete factory syntax. (Closed)

Created:
8 years, 2 months ago by ahe
Modified:
7 years ago
CC:
reviews_dartlang.org, kasperl
Visibility:
Public.

Description

Fix a crash related to obsolete factory syntax.

Patch Set 1 #

Total comments: 6
Unified diffs Side-by-side diffs Delta from patch set Stats (+19 lines, -7 lines) Patch
M dart/lib/compiler/implementation/scanner/class_element_parser.dart View 1 chunk +3 lines, -0 lines 4 comments Download
M dart/lib/compiler/implementation/scanner/listener.dart View 1 chunk +8 lines, -2 lines 0 comments Download
M dart/lib/compiler/implementation/tree/unparser.dart View 1 chunk +5 lines, -3 lines 2 comments Download
M dart/tests/co19/co19-dart2js.status View 2 chunks +2 lines, -2 lines 0 comments Download
M dart/tests/compiler/dart2js/unparser_test.dart View 1 chunk +1 line, -0 lines 0 comments Download

Messages

Total messages: 4 (0 generated)
ahe
Fixes http://dartbug.com/5017.
8 years, 2 months ago (2012-10-12 15:33:22 UTC) #1
karlklose
LGTM. https://codereview.chromium.org/11117022/diff/1/dart/lib/compiler/implementation/tree/unparser.dart File dart/lib/compiler/implementation/tree/unparser.dart (right): https://codereview.chromium.org/11117022/diff/1/dart/lib/compiler/implementation/tree/unparser.dart#newcode274 dart/lib/compiler/implementation/tree/unparser.dart:274: if (node.argumentsNode != null) { You could add ...
8 years, 2 months ago (2012-10-15 07:59:25 UTC) #2
Lasse Reichstein Nielsen
lgtm https://codereview.chromium.org/11117022/diff/1/dart/lib/compiler/implementation/scanner/class_element_parser.dart File dart/lib/compiler/implementation/scanner/class_element_parser.dart (right): https://codereview.chromium.org/11117022/diff/1/dart/lib/compiler/implementation/scanner/class_element_parser.dart#newcode89 dart/lib/compiler/implementation/scanner/class_element_parser.dart:89: SourceString getMethodNameHack(Node methodName) { A method with a ...
8 years, 2 months ago (2012-10-15 08:34:37 UTC) #3
ahe
8 years, 2 months ago (2012-10-15 20:39:15 UTC) #4
Thank you for your suggestions. I think Karl already submitted this CL for me
(thank you). So I'll follow up with a new CL to tweak the unparser. 

As for the hack-method, I really hope I can remove it this week.

https://codereview.chromium.org/11117022/diff/1/dart/lib/compiler/implementat...
File dart/lib/compiler/implementation/scanner/class_element_parser.dart (right):

https://codereview.chromium.org/11117022/diff/1/dart/lib/compiler/implementat...
dart/lib/compiler/implementation/scanner/class_element_parser.dart:89:
SourceString getMethodNameHack(Node methodName) {
On 2012/10/15 08:34:37, Lasse Reichstein Nielsen wrote:
> A method with a name like this *needs* documentation.
> Most other methods would benefit too, but here it's completely unobvious what
it
> does (it returns a Hack?)

I have been focused on removing this method. This requires two things: no
mangling of operator names (I already have a CL for that); also, we should store
constructors by their name. I have been working on that, and I think it is
possible now (we only have two factory classes left: String and List).

https://codereview.chromium.org/11117022/diff/1/dart/lib/compiler/implementat...
dart/lib/compiler/implementation/scanner/class_element_parser.dart:102: if
(receiver == null) {
On 2012/10/15 08:34:37, Lasse Reichstein Nielsen wrote:
> What is it that isn't implemented? 

Library prefixes in factory names. The error message will highlight the prefix,
so I think the error message is good enough for now (this method will be removed
ASAP).

Powered by Google App Engine
This is Rietveld 408576698