wasm-bindgen/crates/macro/ui-tests/unused-attributes.rs

use wasm_bindgen::prelude::*;

struct A;

#[wasm_bindgen]
impl A {
    #[wasm_bindgen(method)]
    #[wasm_bindgen(method)]
    pub fn foo() {
    }
}

fn main() {}
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			`use wasm_bindgen::prelude::*;`

Fix conditional #[wasm_bindgen] in impls Reported in #1191 the fix requires us to get a bit creative I think. The general gist is that a block like this: #[wasm_bindgen] impl Foo { pub fn foo() {} } was previously expanded all in one go. Now, however, it's expanded into: impl Foo { #[__wasm_bindgen_class_marker(Foo = "Foo")] pub fn foo() {} } // goop generated by orginal #[wasm_bindgen] This method of expansion takes advantage of rustc's recursive expansion feature. It also allows us to expand `impl` blocks and allow inner items to not be fully expanded yet, such as still having `#[cfg]` attributes (like in the original bug report). We use theinternal `__wasm_bindgen_class_marker` to indicate that we're parsing an `ImplItemMethod` unconditionally, and then generation proceeds as usual. The only final catch is that when we're expanding in an `impl` block we have to generate tokens for the `Program` (wasm-bindgen injected goop like the custom section) inside the body of the function itself instead of next to it. Otherwise we'd get syntax errors inside of impl blocks! Closes #1191 2019-01-25 14:31:50 -08:00			`struct A;`

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			`#[wasm_bindgen]`
			`impl A {`
			`#[wasm_bindgen(method)]`
			`#[wasm_bindgen(method)]`
			`pub fn foo() {`
			`}`
			`}`
Migrate to `trybuild` from `compiletest` This migrates our UI tests to the recently published `trybuild` crate which should hopefully be a bit more robust than `compiletest` over time! 2019-05-15 14:46:03 -07:00
			`fn main() {}`