Array / record support

[Autumnlight02]

Will things like arrays of structs be possible or a key value store where we have any key but an struct value? or would these things still need to be passed on via postmessage?

[acutmore]

Hi @Autumnlight02, the proposal currently includes another new construct "shared arrays". These are fixed length arrays that can contain shared values, and are themselves shareable.

https://github.com/tc39/proposal-structs#shared-arrays

[Autumnlight02]

So we will not have anything like maps / sets @acutmore or is that for the next stage? I would like if we could have sets and maps and increase their size by chunks on demand

[acutmore]

I think it's very unlikely that this proposal itself would grow to include Map/Set like collections. More likely to be something investigated by a follow on proposal. Structs and SharedArrays are both fixed size, shared collections that can also be resized would add an extra layer of complexity. If a proposal gets too large it can make it difficult to make progress (of course there are also downsides to splitting into lots of micro-proposals too).

I suspect the use cases that need this functionality will initially implement them on top of Shared{Structs/Arrays}. Using a tree/skip-list and a user-land hashing function for example.