Make string juxtaposition combine properly with string interpolations.

frog/leg/resolver.dart

Index: frog/leg/resolver.dart
diff --git a/frog/leg/resolver.dart b/frog/leg/resolver.dart
index 3b3e8a64243d28a4ddc0401f62023f8723c55175..8c365df65f336c233a3167ff3bdcf575314777ec 100644
--- a/frog/leg/resolver.dart
+++ b/frog/leg/resolver.dart
@@ -917,6 +917,10 @@ class ResolverVisitor extends CommonResolverVisitor<Element> {
   visitLiteralNull(LiteralNull node) {
   }
 
+  visitStringJuxtaposition(StringJuxtaposition node) {
+    if (node.isInterpolation) node.visitChildren(this);

[ahe, 2012/03/19 15:53:06]

Is "if (node.isInterpolation)" a "premature" optimization?

[Lasse Reichstein Nielsen, 2012/03/20 09:34:33]

Yes.
All optimizations not backed by measurement are premature.
It used to be a safe and quick check, but after the recent change, making
isInterpolation dynamically computed, it's probably not any faster (apart from
computing isInterpolation so it's cached next time it's read).
I'll remove it.

+  }
+
   visitNodeList(NodeList node) {
     for (Link<Node> link = node.nodes; !link.isEmpty(); link = link.tail) {
       visit(link.head);