Skip to main content

VM to remove support for String + operator by June 17th

Posted by Seth Ladd

Today, the Dart VM team announced they will be removing support for String + operator from the VM on June 17th. In an email to the misc@dartlang.org group, Matthias Hausner wrote:

"On Sunday, June 17, we will turn off support for the String + operator in the VM compiler and runtime. Any code that still uses + will break.

You can test now whether your code is free of String + by invoking the VM with --allow_string_plus=false, or by locally editing runtime/vm/parser.cc and setting the default value of this flag to false and recompile the VM. Then, run your code and fix any fallout."

Rationale

After careful consideration, the string operator+ was removed because:
  • It causes puzzlers (exhibit A)
  • It's superfluous in the presence of string interpolation.
  • It encourages people to write inherently inefficient (quadratic) code.
Alternatives

You have three options to construct Strings, in the absence of the + operator.

String interpolation

String interpolation is great when you need to construct a simple string using other values. For example:


var to = 'Dart developer';
var msg = 'Hello $to!';
assert(msg == 'Hello Dart developer!');

StringBuffer

A StringBuffer allows you to build up a string without actually constructing a string instance. For example:

var to = 'Dart developer';
var buffer = new StringBuffer();
buffer.add('Hello ');
buffer.add(to);
buffer.add('!');
var msg = buffer.toString();
assert(msg == 'Hello Dart developer!');

String buffers are useful when you're building a string using a loop.

Adjacent string literals

When you have long string literals that should be split across different lines, the Dart runtimes will automatically concatenate adjacent string literals.

var longMessage = 'This is a long message that might exceed 80 '
                  'characters because I have '
                  'so much to say, so I split it across many '
                  'lines using adjacent string literals';

While Dart does support the triple-quote string (which allows you to write strings across many lines), sometimes you want to control leading and trailing spacing. In those cases, adjacent string literals is very useful.

Thanks for working with Dart! As always, the Dart discussion list is open for your thoughts and feedback.

Popular posts from this blog

Dart in 2016: The fastest growing programming language at Google, 2nd fastest growing in TIOBE Index

Dart was the fastest growing programming language at Google in 2016 with millions of lines of code written. It also made it to TIOBE Index Top 20 this month (see TIOBE's methodology).

It takes time to build something as ambitious as Dart and, in some ways, Dart is still in its infancy. But we're glad the hard work is starting to pay off.

Many thanks to our amazing community!

We're going to celebrate by ... releasing 1.22 next week (as per our usual 6 week release schedule).

A stronger Dart for everyone

We are constantly asking ourselves:
How do we make developers even more productive when writing Dart apps? We believe that a critical part of the answer to this question is to make strongmode – a sound static type system for Dart – the standard for all Dart developers.

Teams that use Dart to build apps like Soundtrap, AdWords, AdSense, and Greentea say they really enjoy using strong mode features, such as early error detection. In fact, teams that have switched completely to strong mode cite not only early error detection but also better code readability and maintainability as major benefits. We hear this both from small teams and Рeven more so Рfrom large teams with hundreds of developers writing and maintaining millions of lines of Dart code. As Björn Sperber from Soundtrap says,
Strong mode and the smooth integration with IntelliJ is a joy to use and a huge improvement. If you’ve tried out Flutter, you’ve already used strong mode checks from the Dart analyzer.

Given the benefits …

AngularDart 2.1 and new Components

AngularDart got its own dedicated team 5 months ago. Last month, we launched 2.0 final on the Dart Developer Summit. Today, we’re releasing the first minor release after that: 2.1.

Since the focus of AngularDart is Productivity, Performance, Stability, there are no major breaking changes (see the changelog) — but a lot of behind-the-scenes improvements. Your apps will get slightly smaller and faster (even relative to 2.0 which already made huge strides in size and performance since the compiled-from-TypeScript days).

Many features that AngularJS had to implement for JavaScript and TypeScript are not needed in Dart (because Dart already has those features out-of-the-box). So we’re removing them from AngularDart. Renderer is deprecated in favor of plain-old dart:html. NgPlural is going away — Dart programs can use the package:intl library.

New components

On the Dart Developer Summit, we launched AngularDart Components — the material design widgets Google is using in customer-facing apps …