This section lists units of measurement traditionally used in the United States. In keeping with the Metric Conversion Act of
1975 (15 U.S.C. 205a et seq.) as amended by Omnibus Trade and Competitiveness Act of 1988, the ultimate objective is to make
the International System of Units (SI) the primary measurement system used in the United States.

https://www.unicode.org/reports/tr25/ page 11

Some Greek letters are encoded elsewhere as technical symbols. These include U+00B5 µ MICRO SIGN, U+2126 Ω OHM SIGN, and several characters among the APL functional symbols in the Miscellaneous Technical block. U+03A9 Ω GREEK LETTER CAPITAL OMEGA is the canonical equivalent of U+2126 Ω and its use is preferred. Micro sign is included in several parts of ISO/IEC 8859, and therefore supported in many legacy environments where U+03BC μ GREEK LETTER SMALL MU is not available. Implementations therefore need to be able to recognize the micro sign, even though U+03BC μ is the preferred character in a Unicode context.

Hmm but as with all things unicode it's not so simple: https://www.unicode.org/versions/Unicode17.0.0/core-spec/chapter-7/

For compatibility purposes, a few Greek letters are separately encoded as symbols in other character blocks. Examples include U+00B5 µ MICRO SIGN in the Latin-1 Supplement character block and U+2126 Ω OHM SIGN in the Letterlike Symbols character block. The ohm sign is canonically equivalent to the capital omega, and normalization would remove any distinction. Its use is therefore discouraged in favor of capital omega. The same equivalence does not exist between micro sign and mu, and use of either character as a micro sign is common.

With the addition of \Z to RegExp buffer boundaries yesterday I realized there is one small design question that still needs to be addressed. I've regularly promoted \Z as matching (?-m:$|\r?\n$), however this isn't consistent with how $ matches LineTerminator in /m ([\n\r\u2028\u2029]), and is specified to allow CRLF. CRLF support is inconsistently supported across other RegEx implementations:

• Java and .NET match CR, LF, and CRLF
• Perl, PCRE, and PCRE2 may match CRLF based on the configured newline convention
• Ruby only supports LF, but relies on line terminator normalization
• Python only supports LF

I've opened an issue here: https://github.com/tc39/proposal-regexp-buffer-boundaries/issues/20

I can either re-present \Z with modified semantics and ask for consensus or withdraw \Z and advance it separately to give time for discussion.

https://github.com/tc39/proposal-amount/pull/102#discussion_r3133298432

U+2205 is specifically the code point named "EMPTY SET", and is potentially confusable with U+2300 DIAMETER SIGN ⌀, U+00D8 LATIN CAPITAL LETTER O WITH STROKE Ø, and U+00F8 LATIN SMALL LETTER O WITH STROKE ø

I believe the only way this would work is that either:

• if they both import bar, they actually re-evaluate it and get two separate copies of it (as if there were two separate modules that just happened to have the same contents), each with their own cealing
• the first importer gives bar the scope celiling and then that's it even if it's imported again

Nicolò's first AsyncContext example is probably the best introduction I've ever seen

const myVar = new AsyncContext.Variable();

myVar.run('foo', () => doSomething());
myVar.run('bar', () => doSomethingElse());

async function doSomething() {
  await randomSeconds();
  console.log('In doSomething, myVar =', myVar.get());
}
async function doSomethingElse() {
  await randomSeconds();
  console.log('In doSomethingElse, myVar =', myVar.get());
}

One option that we could have is, if we do only module declarations and not module expressions, say that module declarations to not give you any reified value. It would solve the bundling use case, as they would just use import declarations to import the module declarations.

However, it would then only solve the worker use case when paired with this proposal (without being blocked by it), as you would use import source to get a handle to a module declaration.

used by companies you’ve heard of