|
1 | 1 | # Augmentation Libraries
|
2 | 2 |
|
3 | 3 |
|
4 |
| -Version: 1.9 (see [Changelog](#Changelog) at end) |
| 4 | +Version: 1.10 (see [Changelog](#Changelog) at end) |
5 | 5 |
|
6 | 6 | Augmentation libraries allow splitting a Dart library into files. Unlike part
|
7 | 7 | files, each augmentation has its [own imports][part imports] and top-level
|
@@ -261,8 +261,10 @@ are in different packages?**
|
261 | 261 | Unlike part files, which can only add entirely new declarations, an augmentation
|
262 | 262 | can also modify existing declarations in the main library. This can mean adding
|
263 | 263 | 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. |
266 | 268 |
|
267 | 269 | Often, an augmentation wants to also preserve and run the code of the original
|
268 | 270 | declaration it augments (hence the name "augmentation"). It may want run before
|
@@ -919,6 +921,10 @@ language and our tools.
|
919 | 921 |
|
920 | 922 | ## Changelog
|
921 | 923 |
|
| 924 | +## 1.10 |
| 925 | + |
| 926 | +* Make `augment` a built-in identifier. |
| 927 | + |
922 | 928 | ### 1.9
|
923 | 929 |
|
924 | 930 | * Specify that documentation comments are allowed, and should be considered to
|
|
0 commit comments