wasm-bindgen/no_interface.js at ae6f4a9c8726c0a3c69b8597a1c4f667fc9f4d25 - wasm-bindgen - Gitea: Git with a cup of tea

fluencelabs/wasm-bindgen

mirror of https://github.com/fluencelabs/wasm-bindgen synced 2025-06-25 18:51:35 +00:00

Files

.cargo

benchmarks

ci

crates

anyref-xform

backend

cli

cli-support

futures

js-sys

macro

macro-support

multi-value-xform

shared

test

test-macro

threads-xform

typescript-tests

wasm-conventions

wasm-interpreter

web-sys

webidl

webidl-tests

Cargo.toml

array.js

array.rs

array.webidl

array_buffer.js

array_buffer.rs

array_buffer.webidl

build.rs

callbacks.js

callbacks.rs

callbacks.webidl

consts.js

consts.rs

consts.webidl

dictionary.js

dictionary.rs

dictionary.webidl

enums.js

enums.rs

enums.webidl

global.js

global.rs

global.webidl

lib.rs

main.rs

namespace.js

namespace.rs

namespace.webidl

no_interface.js

no_interface.rs

no_interface.webidl

simple.js

simple.rs

simple.webidl

throws.js

throws.rs

throws.webidl

examples

guide

releases

src

tests

.gitattributes

.gitignore

CHANGELOG.md

CONTRIBUTING.md

Cargo.toml

LICENSE-APACHE

LICENSE-MIT

README.md

_package.json

azure-pipelines.yml

build.rs

publish.rs

Alex Crichton 01a52233d3 Support [NoInterfaceObject] in web-sys

This commit enables `[NoInterfaceObject]` annotated interfaces in
`web-sys`. The `NoInterfaceObject` attribute means that there's not
actually a JS class for the object, but all of its properties and such
can still be accessed structually and invoked. This should help provide
more bindings for some more common types on the web!

Note that this builds on recent features to ensure that `dyn_into` and
friends always fail for `NoInterfaceObject` objects because they don't
actually have a class.

Closes #893
Closes #1257
Closes #1315

2019-04-15 10:36:01 -07:00

9 lines

119 B

JavaScript

Raw Blame History

 global.GetNoInterfaceObject = class {
   static get() {
     return {
       number: 3,
       foo: () => {},
     }
   }
 };