Re: [heycam/webidl] non-readonly [FrozenArray] attributes are footguns as currently specced (#810)

Thanks.  I can see the problem if sequences do not have identifying handles.

I'm trying to understand in "a FrozenArray-to-ES conversion takes a sequence as input, creates a frozen JS Array from it, and caches it" where the result would be cached.

Is there a proposed description of [Cached]?

Does [Cached] indicate that the language binding for an attribute (for example, or only attributes even) should cache?
And each specification would indicate when the language binding caches should be invalidated (if required)?

I can see how that would not extend well to callback parameters.

Currently,
```
callback MyCallback = void ( FrozenArray<FrozenArray<Item>> parameter )
```
would pass by reference to an ECMAScript callback.
I understand the proposal here would change that to pass by copy.
Specifications preferring pass by reference could still retain the same behavior through
```
callback MyCallback = void ( object parameter )
```
That is arguably more informative, because it is clearly an Object, and less informative, because the nature of the Object would need more description in prose.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/issues/810#issuecomment-538211649