File tree 1 file changed +7
-5
lines changed
1 file changed +7
-5
lines changed Original file line number Diff line number Diff line change @@ -215,13 +215,15 @@ Thread safety of Cleaners and native code
215
215
### Design
216
216
217
217
<a name =" rationalize " ></a >
218
- [ #] ( #rationalize ) Dn.1. If the patch introduces a new subsystem with concurrent code, is ** the
219
- necessity for concurrency or thread safety rationalized in the patch description** ? Is there a
220
- discussion of alternative design approaches that could simplify the concurrency model of the code
221
- (see the next item)?
218
+ [ #] ( #rationalize ) Dn.1. If the patch introduces a new subsystem (class, method) with concurrent
219
+ code, is ** the necessity for concurrency or thread safety rationalized in the patch description** ?
220
+ Is there a discussion of alternative design approaches that could simplify the concurrency model of
221
+ the code (see the next item)?
222
222
223
223
A way to nudge thinking about concurrency design is demanding the usage of concurrency tools and
224
- language constructs be [ justified in comments] ( #justify-document ) .
224
+ language constructs to be [ justified in comments] ( #justify-document ) .
225
+
226
+ See also an item about [ unneeded thread-safety of classes and methods] ( #unneeded-thread-safety ) .
225
227
226
228
<a name =" use-patterns " ></a >
227
229
[ #] ( #use-patterns ) Dn.2. Is it possible to apply one or several design patterns (some of them are
You can’t perform that action at this time.
0 commit comments