TC39 Module Harmony
2024-06-14
plaintext logs
prev next
source on github
09:58
<guybedford>
https://github.com/guybedford/proposal-export-star-default was my attempt previously, but without the ** semantics, which may well get more attention. Aapo Alasuutari if you would like to work on a new proposal I'm sure one of us could try champion it for you.
10:47
<Aapo Alasuutari>
https://github.com/guybedford/proposal-export-star-default was my attempt previously, but without the ** semantics, which may well get more attention. Aapo Alasuutari if you would like to work on a new proposal I'm sure one of us could try champion it for you.

Hmm, an issue mentions:

But, the committee was very clear that having an ambiguous statement that doesn't tell the reader whether or not there is a default or not, it a no-go. In other words, you will have to specify whether or not you want the default to be defined.

10:48
<Aapo Alasuutari>
So the single-line export without explicitly mentioned default wouldn't be acceptable according to this?
12:29
<nicolo-ribaudo>
We should go find the relevant notes in the tc39/notes repo and read the discussion
16:09
<nicolo-ribaudo>

guybedford I was talking with Luca and we have different understanding of how module identity is preserved across cloning. Do you expect this to be true or false?

import source x from "./x.js";
await import(x) === await import(structureClone(x));
16:09
<Jack Works>
it depends on the host (web api)?
16:10
<Jack Works>
I don't have a clear intuitive about what it should be
16:30
<Mathieu Hofman>

guybedford I was talking with Luca and we have different understanding of how module identity is preserved across cloning. Do you expect this to be true or false?

import source x from "./x.js";
await import(x) === await import(structureClone(x));
Any identity preservation through postMessage will likely require implementations to adopt a distributed GC (or make these objects uncollectible)
16:32
<Mathieu Hofman>
Well technically there is another way in this case which is to resolve the identity of these objects to their content, but that would require changing object equality semantics, which we've already heard browsers balk at for Records and Tuples