There is actually no reason to use `assert.doesNotThrow()` in the tests. If a test throws, just let the error bubble up right away instead of first catching it and then rethrowing it. PR-URL: https://github.com/nodejs/node/pull/18669 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
30 lines
630 B
JavaScript
30 lines
630 B
JavaScript
/*global SharedArrayBuffer*/
|
|
'use strict';
|
|
|
|
require('../common');
|
|
const assert = require('assert');
|
|
|
|
const sab = new SharedArrayBuffer(24);
|
|
const arr1 = new Uint16Array(sab);
|
|
const arr2 = new Uint16Array(12);
|
|
arr2[0] = 5000;
|
|
arr1[0] = 5000;
|
|
arr1[1] = 4000;
|
|
arr2[1] = 4000;
|
|
|
|
const arr_buf = Buffer.from(arr1.buffer);
|
|
const ar_buf = Buffer.from(arr2.buffer);
|
|
|
|
assert.deepStrictEqual(arr_buf, ar_buf);
|
|
|
|
arr1[1] = 6000;
|
|
arr2[1] = 6000;
|
|
|
|
assert.deepStrictEqual(arr_buf, ar_buf);
|
|
|
|
// Checks for calling Buffer.byteLength on a SharedArrayBuffer
|
|
|
|
assert.strictEqual(Buffer.byteLength(sab), sab.byteLength);
|
|
|
|
Buffer.from({ buffer: sab });
|