mirror of
https://github.com/fluencelabs/wasm-bindgen
synced 2025-04-28 23:22:16 +00:00
93a510ef93
This information is embedded within the algorithm for constructing interfaces and their prototypes in the section for ECMAScript glue in the WebIDL spec... This really *should* make the `wasm_bindgen_backend::ast::ImportType::extends` member from a `Vec<Ident>` into a `Vec<syn::Path>` so that we could use `js_sys::Object` in the extends field, but that is a huge pain because then the `ImportedTypes` trait needs to be changed, and all of its implementers, etc...
21 lines
834 B
Rust
Executable File
21 lines
834 B
Rust
Executable File
//! Raw API bindings for Web APIs
|
|
//!
|
|
//! This is a procedurally generated crate from browser WebIDL which provides a
|
|
//! binding to all APIs that browser provide on the web.
|
|
//!
|
|
//! This crate by default contains very little when compiled as almost all of
|
|
//! its exposed APIs are gated by Cargo features. The exhaustive list of
|
|
//! features can be found in `crates/web-sys/Cargo.toml`, but the rule of thumb
|
|
//! for `web-sys` is that each type has its own cargo feature (named after the
|
|
//! type). Using an API requires enabling the features for all types used in the
|
|
//! API, and APIs should mention in the documentation what features they
|
|
//! require.
|
|
|
|
#![doc(html_root_url = "https://docs.rs/web-sys/0.2")]
|
|
|
|
extern crate wasm_bindgen;
|
|
extern crate js_sys;
|
|
use js_sys::Object;
|
|
|
|
include!(concat!(env!("OUT_DIR"), "/bindings.rs"));
|