Skip to main content

Proposal to add metadata to Dart language

Posted by Peter von der Ahé

Disclaimer: This is an early proposal, it is not in the Dart language spec yet. This might change or be retracted. Comments welcome!

UPDATE: Join the discussion about this proposal on the Dart mailing list.

Dart Metadata Level 1

We propose to add metadata in the form of constant expressions prefixed with ‘@’. For example:

class Object {
  …
 @native int hashCode();
}

In the example above, the metadata is highlighted in blue.

The grammatical rule for metadata is:

metadata: '@' expression ;

The expression must be a constant expression.

The example above assumes these additional declarations:

class Native {
 const Native();
}

const native = const Native();

Informally, metadata can appear before a class, interface, typedef, constructor, factory, function, field, parameter, or variable declaration. For example:

@metadata
interface MyInterface {
 @metadata var field;
 @metadata get getter();
 @metadata String method(@metadata parameter, [@metadata optional]);
}

@42
class MyClass {
 @metadata MyClass(@metadata parameter) {
   @metadata localFunction() => 42;
   @metadata var variable = null;
   for (@metadata var i in [1, 2, 3]) {
     print(i);
   }
 }
}

Since metadata can be any constant expression, the following is possible:

@const <int>[1, 2, 3]
class MyOtherClass {
}

Metadata is fully reified and available through mirror-based reflection, in other words, unless reflection is enabled, metadata can be ignored.

Q: Can I access metadata on local variables?
A: It depends: Does the mirror API expose AST nodes? Most likely not, initially.

Q: Can I access metadata on a local function?
A: An object mirror on a closurized local function should be able to return the metadata of the corresponding function declaration. In addition, if the mirror API exposes AST nodes, such AST nodes will include the metadata.

Open question: what about raw strings?



As always, please join the discussion on the Dart mailing list.

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).

The new Google AdSense user interface: built with AngularDart

AdSense is a free, simple way to earn money by placing ads on your website. The team just launched a completely new version of their app for publishers. Read all about it here. We asked Daniel White, the tech lead for the project, some questions because the new UI happens to be built with Dart and Angular2.


AdSense launched way back in 2003. How long is it since the last big redesign?
Last big redesign was called ‘AdSense 3’ and launched about 6 years ago. It was written in Google Web Toolkit (GWT) and the UI has evolved through several iterations - but this is the first ground-up redesign in 6 years. There are a number of long-standing UX issues that we’ve taken the opportunity to solve. A big shout-out to our UX team who’ve been 100% behind this project. We couldn’t have done it without them!

How many software engineers worked on the project?
Purely on the AdSense applications, we have a team of close to 100. Around 25% of them write Dart.

How many lines of code?
We have around 160K LO…

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 …