Rename ClosureClassMaps to ClosureDataLookup

pkg/compiler/lib/src/closure.dart

Index: pkg/compiler/lib/src/closure.dart
diff --git a/pkg/compiler/lib/src/closure.dart b/pkg/compiler/lib/src/closure.dart
index 618ae7c20f94455e100cf42fabeef2120b391870..c34aacf3908a0c186fccf26e62247b216a56f459 100644
--- a/pkg/compiler/lib/src/closure.dart
+++ b/pkg/compiler/lib/src/closure.dart
@@ -2,7 +2,7 @@
 // for details. All rights reserved. Use of this source code is governed by a
 // BSD-style license that can be found in the LICENSE file.
 
-library closureToClassMapper;
+library closureDataLookup;

[Siggi Cherem (dart-lang), 2017/06/14 23:17:12]

nit: the convention is to use a lower.case.name.with.dots_and_underscores. Here
I'd use:

compiler.src.closure or compiler.src.closure_data;

we could also just drop the library tag here, it is not needed. I only include
it when I want to have a library-level dartdoc

[Emily Fortuna, 2017/06/14 23:44:13]

removed

 
 import 'common/names.dart' show Identifiers;
 import 'common/resolution.dart' show ParsingContext, Resolution;
@@ -25,9 +25,11 @@ import 'tree/tree.dart';
 import 'util/util.dart';
 import 'world.dart' show ClosedWorldRefiner;
 
-/// Where T is ir.Node or Node.
-// TODO(efortuna): Rename this class.
-abstract class ClosureClassMaps<T> {
+/// Class that provides information for how closures are rewritten/represented
+/// to preserve Dart semantics in other situations. Given a particular node to

[Siggi Cherem (dart-lang), 2017/06/14 23:17:12]

not sure I follow the prat "in other situations" here. Maybe replace with "when
compiled to JavaScript"?

[Emily Fortuna, 2017/06/14 23:44:13]

Done.

+/// look up, it returns a information about the internal representation of how
+/// closure conversion is implemented. T is an ir.Node or Node.
+abstract class ClosureDataLookup<T> {

[Siggi Cherem (dart-lang), 2017/06/14 23:17:12]

another reason I'd change *Info below to *Data :-)

[Emily Fortuna, 2017/06/14 23:44:13]

I messaged you in chat about this:

For me, as a native English speaker, "data" has a slightly different sense than
"info", which is why I used one in one place and one in the other. 

"info" basically always refers to a single bit of information
whereas "data" can refer to to the collective of details
hence me using "info" in one place and "data" in the other
do you still think I should keep it "data" throughout?

[Siggi Cherem (dart-lang), 2017/06/15 00:09:01]

Thanks, to bring the full loop of the discussion: "info" sgtm :) - we should
review existing uses of Data elsewhere in the compiler and change to Info if
they fit in a similar category. Very low-pri though :)

   /// Look up information about the variables that have been mutated and are
   /// used inside the scope of [node].
   // TODO(johnniwinther): Split this up into two functions, one for members and
@@ -194,7 +196,7 @@ class ClosureRepresentationInfo {
   bool get isClosure => false;
 }
 
-class ClosureTask extends CompilerTask implements ClosureClassMaps<Node> {
+class ClosureTask extends CompilerTask implements ClosureDataLookup<Node> {
   Map<Node, ClosureScope> _closureInfoMap = <Node, ClosureScope>{};
   Map<Element, ClosureClassMap> _closureMappingCache =
       <Element, ClosureClassMap>{};