fluencelabs/wasm-bindgen
1
0
Fork 0
mirror of https://github.com/fluencelabs/wasm-bindgen synced 2025-03-18 03:00:50 +00:00
Code Issues Projects Releases Wiki Activity
wasm-bindgen/crates/macro/Cargo.toml

24 lines
692 B
TOML
Raw Permalink Normal View History

Initial commit
2017-12-14 19:31:01 -08:00
[package]
name = "wasm-bindgen-macro"
Bump to 0.2.39
2019-03-13 11:02:27 -07:00
version = "0.2.39"
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
authors = ["The wasm-bindgen Developers"]
Prep work for the 0.1 release
2018-03-05 20:24:35 -08:00
license = "MIT/Apache-2.0"
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
repository = "https://github.com/rustwasm/wasm-bindgen/tree/master/crates/macro"
homepage = "https://rustwasm.github.io/wasm-bindgen/"
Prep work for the 0.1 release
2018-03-05 20:24:35 -08:00
documentation = "https://docs.rs/wasm-bindgen"
description = """
Definition of the `#[wasm_bindgen]` attribute, an internal dependency
"""
Initial commit
2017-12-14 19:31:01 -08:00
[lib]
proc-macro = true
Add `spans` feature to control `proc-macro2` Using `proc-macro2`'s `nightly` feature is a good default for most use cases. However, it causes a build error if used together with crates such as `cssparser` that also use `proc-macro2` from a build script. This change adds a default enabled feature `spans` that users can disable if they need to work around this conflict. Fixes #160.
2018-04-25 14:42:13 -05:00
[features]
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
spans = ["wasm-bindgen-macro-support/spans"]
Add a feature for printing the macro's generated code (#212)
2018-05-25 16:17:54 -07:00
xxx_debug_only_print_generated_code = []
Assert all attributes are used by default This commit implements a system that will assert that all `#[wasm_bindgen]` attributes are actually used during compilation. This should help ensure that we don't sneak in stray attributes that don't actually end up having any meaning, and hopefully make it a bit easier to learn `#[wasm_bindgen]`!
2018-11-27 15:14:59 -08:00
strict-macro = ["wasm-bindgen-macro-support/strict-macro"]
Add `spans` feature to control `proc-macro2` Using `proc-macro2`'s `nightly` feature is a good default for most use cases. However, it causes a build error if used together with crates such as `cssparser` that also use `proc-macro2` from a build script. This change adds a default enabled feature `spans` that users can disable if they need to work around this conflict. Fixes #160.
2018-04-25 14:42:13 -05:00
Initial commit
2017-12-14 19:31:01 -08:00
[dependencies]
Bump to 0.2.39
2019-03-13 11:02:27 -07:00
wasm-bindgen-macro-support = { path = "../macro-support", version = "=0.2.39" }
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
quote = "0.6"
Reference in New Issue Copy Permalink