Skip to content

Commit 96151bd

Browse files
committed
Remove old XXX markers
1 parent 1a168fd commit 96151bd

File tree

1 file changed

+0
-9
lines changed

1 file changed

+0
-9
lines changed

TSPL.docc/LanguageGuide/Concurrency.md

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1087,16 +1087,9 @@ Task { @MainActor in
10871087
}
10881088
```
10891089

1090-
<!-- XXX TR: Should we show a detached task here instead? -->
1091-
10921090
The code above is similar to
10931091
`downloadAndShowPhoto(named:)` from the previous code listing,
10941092
but the code in this example doesn't wait for the UI update.
1095-
<!--
1096-
XXX more explanation of the difference?
1097-
Or why you'd use Task to do this kind of thing?
1098-
-->
1099-
11001093
You can also write `@MainActor` on a structure, class, or enumeration
11011094
to ensure all of its methods and all access to its properties
11021095
to run on the main actor:
@@ -1140,8 +1133,6 @@ You'd see the same behavior if `View` were a base class
11401133
and `PhotoGalleryView` were a subclass ---
11411134
the subclass would be implicitly marked `@MainActor`.
11421135

1143-
<!-- XXX TR: Is there a parallel non-UI example, like for server code? -->
1144-
11451136
In the examples above,
11461137
`PhotoGallery` protects the entire structure on the main actor.
11471138
For more fine-grained control,

0 commit comments

Comments
 (0)