Fix kotlin language highlight for CONCURRENCY.md
This commit is contained in:
committed by
SvyatoslavScherbina
parent
801f6a5036
commit
e9c8904445
+3
-3
@@ -94,7 +94,7 @@ future.consume {
|
||||
concurrent threads, if the worker mechanisms are insufficient for a particular task. Note, that object detachment
|
||||
may require explicit leaving function holding object references and then performing cyclic garbage collection.
|
||||
For example, code like:
|
||||
```$kotlin
|
||||
```kotlin
|
||||
val graph = DetachedObjectGraph {
|
||||
val map = mutableMapOf<String, String>()
|
||||
for (entry in map.entries) {
|
||||
@@ -104,7 +104,7 @@ val graph = DetachedObjectGraph {
|
||||
}
|
||||
```
|
||||
will not work as expected and will throw runtime exception, as there are uncollected cycles in the detached graph, while:
|
||||
```$kotlin
|
||||
```kotlin
|
||||
val graph = DetachedObjectGraph {
|
||||
{
|
||||
val map = mutableMapOf<String, String>()
|
||||
@@ -207,4 +207,4 @@ that are potentially parts of shared cyclic data should be zeroed out once no lo
|
||||
If atomic reference value is attempted to be set to non-frozen value runtime exception is thrown.
|
||||
|
||||
Freezable atomic reference is similar to the regular atomic reference, but until frozen behaves like regular box
|
||||
for a reference. After freezing it behaves like an atomic reference, and can only hold a reference to a frozen object.
|
||||
for a reference. After freezing it behaves like an atomic reference, and can only hold a reference to a frozen object.
|
||||
|
||||
Reference in New Issue
Block a user