Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

No need for a [[BackingMap]] in Bluetooth{Manufacturer,Service}DataMap anymore #596

Open
rakuco opened this issue Oct 20, 2022 · 0 comments
Open

No need for a [[BackingMap]] in Bluetooth{Manufacturer,Service}DataMap anymore #596

rakuco opened this issue Oct 20, 2022 · 0 comments

Comments

@rakuco
Copy link

rakuco commented Oct 20, 2022

See whatwg/webidl#1138 and whatwg/webidl#824. Maplike interfaces no longer need to have a [[BackingMap]] internal slot. Instead, as per https://webidl.spec.whatwg.org/#dfn-map-entries, "Objects implementing an interface that is declared to be maplike represent an ordered map of key–value pairs, initially empty, known as that object’s map entries".

In practice, this means the interface's "map entries" can be referenced and manipulated directly using the standard infra language for ordered maps.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rakuco