Skip to content

Commit ff6256e

Browse files
authored
Restore the changes made in version 1.23 which were undone by accident (#3990)
1 parent a3a7c1d commit ff6256e

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

working/augmentation-libraries/feature-specification.md

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

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

66
Augmentations allow spreading your implementation across multiple locations,
77
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:
350350
* **Augmenting operators**: When augmenting an operator, `augmented`
351351
refers to the augmented operator method, which must be immediately
352352
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
354354
operator, and when augmenting `operator []=` you would use the
355-
`augmented[key] = value` syntax.
355+
`augmented(key, value)` syntax.
356356

357357
* Note that `augmented` in such an augmenting operator method body is
358358
not an expression by itself, and cannot be used to tear off the
@@ -1347,6 +1347,10 @@ to the augmentation.
13471347

13481348
## Changelog
13491349

1350+
### 1.26
1351+
1352+
* Recreate the change made in 1.23 (which was undone by accident).
1353+
13501354
### 1.25
13511355

13521356
* Clarify that augmentations can occur in the same type-introducing

0 commit comments

Comments
 (0)