Skip to content

Commit 6b15dcf

Browse files
authored
make augment a built-in identifier (#3054)
Closes #2120
1 parent 5de4ace commit 6b15dcf

File tree

1 file changed

+9
-3
lines changed

1 file changed

+9
-3
lines changed

working/augmentation-libraries/feature-specification.md

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# Augmentation Libraries
22

33
4-
Version: 1.9 (see [Changelog](#Changelog) at end)
4+
Version: 1.10 (see [Changelog](#Changelog) at end)
55

66
Augmentation libraries allow splitting a Dart library into files. Unlike part
77
files, each augmentation has its [own imports][part imports] and top-level
@@ -261,8 +261,10 @@ are in different packages?**
261261
Unlike part files, which can only add entirely new declarations, an augmentation
262262
can also modify existing declarations in the main library. This can mean adding
263263
new members to an existing type, or even modifying the code of an existing
264-
declaration. There are a few supported operations which are all marked
265-
syntactically using an `augment` modifier.
264+
declaration. There is a new built-in identifier, `augment`, which is used to
265+
syntactically mark a declaration as an augmentation of an existing one. The
266+
introduction of this new identifier will be language versioned in order to make
267+
it non-breaking for old code.
266268
267269
Often, an augmentation wants to also preserve and run the code of the original
268270
declaration it augments (hence the name "augmentation"). It may want run before
@@ -919,6 +921,10 @@ language and our tools.
919921

920922
## Changelog
921923

924+
## 1.10
925+
926+
* Make `augment` a built-in identifier.
927+
922928
### 1.9
923929

924930
* Specify that documentation comments are allowed, and should be considered to

0 commit comments

Comments
 (0)