Atomics.compareExchange()
 The static Atomics.compareExchange() method exchanges a given replacement value at a given position in the array, if a given expected value equals the old value. It returns the old value at that position whether it was equal to the expected value or not. This atomic operation guarantees that no other write happens until the modified value is written back. 
Syntax
Atomics.compareExchange(typedArray, index, expectedValue, replacementValue)
Parameters
- typedArray
-  An integer typed array. One of Int8Array,Uint8Array,Int16Array,Uint16Array,Int32Array,Uint32Array,BigInt64Array, orBigUint64Array.
- index
-  The position in the typedArrayto exchange avalue.
- expectedValue
-  The value to check for equality. 
- replacementValue
-  The number to exchange. 
Return value
 The old value at the given position (typedArray[index]). 
Exceptions
-  Throws a TypeError, iftypedArrayis not one of the allowed integer types.
-  Throws a RangeError, ifindexis out of bounds in thetypedArray.
Examples
Using compareExchange()
const sab = new SharedArrayBuffer(1024); const ta = new Uint8Array(sab); ta[0] = 7; Atomics.compareExchange(ta, 0, 7, 12); // returns 7, the old value Atomics.load(ta, 0); // 12
Specifications
Browser compatibility
| Desktop | Mobile | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Chrome | Edge | Firefox | Internet Explorer | Opera | Safari | WebView Android | Chrome Android | Firefox for Android | Opera Android | Safari on IOS | Samsung Internet | |
| compareExchange | 68 60-63 Chrome disabled  SharedArrayBufferon January 5, 2018 to help reduce the efficacy of speculative side-channel attacks. This was a temporary removal while mitigations were put in place. | 79 16-17 Support was removed to mitigate speculative execution side-channel attacks (Windows blog). | 78 57 Support was disabled by default to mitigate speculative execution side-channel attacks (Mozilla Security Blog). 55-57 46-55 | No | No | 10.1-11.1 | 60-63 Chrome disabled  SharedArrayBufferon January 5, 2018 to help reduce the efficacy of speculative side-channel attacks. This is intended as a temporary measure until other mitigations are in place. | 60-63 Chrome disabled  SharedArrayBufferon January 5, 2018 to help reduce the efficacy of speculative side-channel attacks. This is intended as a temporary measure until other mitigations are in place. | 57 Support was disabled by default to mitigate speculative execution side-channel attacks (Mozilla Security Blog). 55-57 46-55 | No | 10.3-11.3 | No Chrome disabled  SharedArrayBufferon January 5, 2018 to help reduce the efficacy of speculative side-channel attacks. This is intended as a temporary measure until other mitigations are in place. | 
See also
    © 2005–2021 MDN contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.
    https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Atomics/compareExchange