fluencelabs/wasm-bindgen
1
0
Fork 0
mirror of https://github.com/fluencelabs/wasm-bindgen synced 2025-04-23 05:02:13 +00:00
Code Issues Projects Releases Wiki Activity
wasm-bindgen/crates/backend/src/lib.rs

29 lines
553 B
Rust
Raw Normal View History

Finish fixing fallout in all tests
2018-03-31 09:04:00 -07:00
#![recursion_limit = "256"]
Run rustfmt over everything
2018-11-27 12:07:59 -08:00
#![cfg_attr(feature = "extra-traits", deny(missing_debug_implementations))]
Bump to 0.2.12 (#515) * Bump to 0.2.12 * Update all version numbers and deps * Update all listed authors to `["The wasm-bindgen Developers"]` * Update `repository` links to specific paths for each crate * Update `homepage` links to the online book * Update all links away from `alexcrichton/wasm-bindgen` * Add `#[doc]` directives for HTML URLs * Update more version requirements * Fill out CHANGELOG
2018-07-19 14:57:04 -05:00
#![doc(html_root_url = "https://docs.rs/wasm-bindgen-backend/0.2")]
Split out the AST and codegen into the wasm-bindgen-backend crate
2018-03-29 09:14:32 -07:00
Remove `unsafe` usage in `backend/src/encode.rs` Using `unsafe` was just a little too eager there so let's use an off-the-shelf solution for solving the actual problem we have, which is to allocate strings with a lifetime of `Interner` rather than deduplicating strings.
2019-03-05 12:27:39 -08:00
extern crate bumpalo;
Translate `ByteString` in WebIDL to `[u8]` (#505) In arguments take `&[u8]` and in return value return `Vec<u8>`. Should help fill out a few more APIs on `Header` and `Response`!
2018-07-18 17:59:24 -05:00
#[macro_use]
extern crate log;
Split out the AST and codegen into the wasm-bindgen-backend crate
2018-03-29 09:14:32 -07:00
extern crate proc_macro2;
#[macro_use]
extern crate quote;
Backend refactor (#411) * remove BindgenAttrs from other backend::ast structs This is primarily a tool for use with the macro crate. Most of these attributes were ignored in the actual codegen, but a few were still being used. This is confusing when trying to add other sources for codegen (such as webidl and typescript). * move parsing logic to macro crate This makes the backend crate solely concerned with having an ast for which we can generate code.
2018-07-07 10:20:31 -07:00
extern crate syn;
Don't use JSON for custom section format This commit migrates away from using Serde for the custom section in wasm executables. This is a refactoring of a purely-internal data structure to `wasm-bindgen` and should have no visible functional change on users. The motivation for this commit is two fold: * First, the compile times using `serde_json` and `serde_derive` for the syntax extension isn't the most fun. * Second, eventually we're going to want to stablize the layout of the custom section, and it's highly unlikely to be json! Primarily, though, the intention of this commit is to improve the cold-cache compile time of `wasm-bindgen` by ensuring that for new users this project builds as quickly as possible. By removing some heavyweight dependencies from the procedural macro, `serde`, `serde_derive`, and `serde_json`, we're able to get a pretty nice build time improvement for the `wasm-bindgen` crate itself: | | single-core build | parallel build | |-------------|-------------------|----------------| | master | 36.5s | 17.3s | | this commit | 20.5s | 11.8s | These are't really end-all-be-all wins but they're much better especially on the spectrum of weaker CPUs (in theory modeled by the single-core case showing we have 42% less CPU work in theory).
2018-08-26 15:43:33 -07:00
#[macro_use]
extern crate lazy_static;
Split out the AST and codegen into the wasm-bindgen-backend crate
2018-03-29 09:14:32 -07:00
Don't use JSON for custom section format This commit migrates away from using Serde for the custom section in wasm executables. This is a refactoring of a purely-internal data structure to `wasm-bindgen` and should have no visible functional change on users. The motivation for this commit is two fold: * First, the compile times using `serde_json` and `serde_derive` for the syntax extension isn't the most fun. * Second, eventually we're going to want to stablize the layout of the custom section, and it's highly unlikely to be json! Primarily, though, the intention of this commit is to improve the cold-cache compile time of `wasm-bindgen` by ensuring that for new users this project builds as quickly as possible. By removing some heavyweight dependencies from the procedural macro, `serde`, `serde_derive`, and `serde_json`, we're able to get a pretty nice build time improvement for the `wasm-bindgen` crate itself: | | single-core build | parallel build | |-------------|-------------------|----------------| | master | 36.5s | 17.3s | | this commit | 20.5s | 11.8s | These are't really end-all-be-all wins but they're much better especially on the spectrum of weaker CPUs (in theory modeled by the single-core case showing we have 42% less CPU work in theory).
2018-08-26 15:43:33 -07:00
#[macro_use]
Split out the AST and codegen into the wasm-bindgen-backend crate
2018-03-29 09:14:32 -07:00
extern crate wasm_bindgen_shared as shared;
Prepare to have targeted error diagnostics (#604) This commit starts to add infrastructure for targeted diagnostics in the `#[wasm_bindgen]` attribute, intended eventually at providing much better errors as they'll be pointing to exactly the code in question rather than always to a `#[wasm_bindgen]` attribute. The general changes are are: * A new `Diagnostic` error type is added to the backend. A `Diagnostic` is created with a textual error or with a span, and it can also be created from a list of diagnostics. A `Diagnostic` implements `ToTokens` which emits a bunch of invocations of `compile_error!` that will cause rustc to later generate errors. * Fallible implementations of `ToTokens` have switched to using a new trait, `TryToTokens`, which returns a `Result` to use `?` with. * The `MacroParse` trait has changed to returning a `Result` to propagate errors upwards. * A new `ui-tests` crate was added which uses `compiletest_rs` to add UI tests. These UI tests will verify that our output improves over time and does not regress. This test suite is added to CI as a new builder as well. * No `Diagnostic` instances are created just yet, everything continues to panic and return `Ok`, with the one exception of the top-level invocations of `syn::parse` which now create a `Diagnostic` and pass it along. This commit does not immediately improve diagnostics but the intention is that it is laying the groundwork for improving diagnostics over time. It should ideally be much easier to contribute improved diagnostics after this commit! cc #601
2018-08-01 17:15:27 -05:00
pub use codegen::TryToTokens;
pub use error::Diagnostic;
Convert some more macro panics to diagnostics (#611) This should hopefully be the last of the manually written diagnostics!
2018-08-02 11:12:50 -05:00
#[macro_use]
mod error;
Split out the AST and codegen into the wasm-bindgen-backend crate
2018-03-29 09:14:32 -07:00
pub mod ast;
mod codegen;
Create the `web-sys` crate mechanically from WebIDL (#409) * Create a new `web-sys` crate This will eventually contain all the WebIDL-generated bindings to Web APIs. * ci: Test the new `web-sys` crate in CI * web-sys: Add a small README * web-sys: Vendor all the WebIDL files from mozilla-central * backend: Add a pass to remove AST items that use undefined imports This is necessary for the WebIDL frontend, which can't translate many WebIDL constructs into equivalent wasm-bindgen AST things yet. It lets us make incremental progress: we can generate bindings to methods we can support right now even though there might be methods on the same interface that we can't support yet. * webidl: Add a bunch of missing semicolons * webidl: Make parsing private It was only `pub` so that we could test it, but we ended up moving towards integration tests rather than unit tests that assert particular ASTs are parsed from WebIDL files. * webidl: Remove uses of undefined import types * test-project-builder: Build projects in "very verbose" mode This helps for debugging failing WebIDL-related tests. * test-project-builder: Add more profiling timers * test-project-builder: Detect when webpack-dev-server fails Instead of going into an infinite loop, detect when webpack-dev-server fails to start up and early exit the test. * webidl: Specify version for dev-dependency on wasm-bindgen-backend Instead of only a relative path. * guide: Add section about contributing to `web-sys` * WIP enable Event.webidl Still need to fix and finish the test. * Update expected webidl output * Start out a test's status as incomplete That way if we don't fill it in the error message doesn't look quite so bizarre * Fix onerror function in headless mode Otherwise we don't see any output! * Fix package.json/node_modules handling in project generation Make sure these are looked up in the git project root rather than the crate root * Avoid logging body text This was meant for debugging and is otherwise pretty noisy * Fix a relative path * More expected test fixes * Fix a typo * test-project-builder: Allow asynchronous tests * webidl: Convert [Unforgeable] attributes into `#[wasm_bindgen(structural)]` Fixes #432 * test-project-builder: Print generated WebIDL bindings for debugging purposes Helps debug bad WebIDL bindings generation inside tests. * When we can't find a descriptor, say which one can't be found This helps when debugging things that need to become structural. * web-sys: Test bindings for Event * ci: Use `--manifest-path dir` instead of `cd dir && ...` * web-sys: Just move .webidl files isntead of symlinking to enable them * tests: Polyfill Array.prototype.values for older browsers in CI * test-project-builder: Don't panic on poisoned headless test mutex We only use it to serialize headless tests so that we don't try to bind the port concurrently. Its OK to run another headless test if an earlier one panicked. * JsValue: Add {is,as}_{object,function} methods Allows dynamically casting values to `js::Object` and `js::Function`. * tidy: Fix whitespace and missing semicolons * Allow for dynamic feature detection of methods If we create bindings to a method that doesn't exist in this implementation, then it shouldn't fail until if/when we actually try and invoke that missing method. * tests: Do feature detection in Array.prototype.values test * Add JsValue::{is_string, as_js_string} methods And document all the cast/convert/check methods for js value. * eslint: allow backtick string literals * Only generate a fallback import function for non-structural imports
2018-07-09 16:35:25 -07:00
pub mod defined;
Run rustfmt over everything
2018-11-27 12:07:59 -08:00
mod encode;
Move some utility functions from the webidl crate into the backend crate
2018-06-25 10:41:33 -07:00
pub mod util;
Reference in New Issue Copy Permalink