|
1 | 1 | # Augmentations |
2 | 2 |
|
3 | 3 | Author: rnystrom@google.com, jakemac@google.com, lrn@google.com <br> |
4 | | -Version: 1.25 (see [Changelog](#Changelog) at end) |
| 4 | +Version: 1.26 (see [Changelog](#Changelog) at end) |
5 | 5 |
|
6 | 6 | Augmentations allow spreading your implementation across multiple locations, |
7 | 7 | both within a single file and across multiple files. They can add new top-level |
@@ -350,9 +350,9 @@ augmented, but it generally follows the same rules as any normal identifier: |
350 | 350 | * **Augmenting operators**: When augmenting an operator, `augmented` |
351 | 351 | refers to the augmented operator method, which must be immediately |
352 | 352 | invoked using function call syntax. For example, when augmenting |
353 | | - `operator +` you could use `augmented + 1` to call the augmented |
| 353 | + `operator +` you could use `augmented(1)` to call the augmented |
354 | 354 | operator, and when augmenting `operator []=` you would use the |
355 | | - `augmented[key] = value` syntax. |
| 355 | + `augmented(key, value)` syntax. |
356 | 356 |
|
357 | 357 | * Note that `augmented` in such an augmenting operator method body is |
358 | 358 | not an expression by itself, and cannot be used to tear off the |
@@ -1347,6 +1347,10 @@ to the augmentation. |
1347 | 1347 |
|
1348 | 1348 | ## Changelog |
1349 | 1349 |
|
| 1350 | +### 1.26 |
| 1351 | + |
| 1352 | +* Recreate the change made in 1.23 (which was undone by accident). |
| 1353 | + |
1350 | 1354 | ### 1.25 |
1351 | 1355 |
|
1352 | 1356 | * Clarify that augmentations can occur in the same type-introducing |
|
0 commit comments