wasm-bindgen/crates/macro/ui-tests/invalid-setter.stderr

error: setters must start with `set_`, found: a
  --> $DIR/invalid-setter.rs:12:8
   |
12 |     fn a(this: &A, b: i32);
   |        ^

error: aborting due to previous error
Improve error message for `infer_setter_property` If the setter doesn't start with `set_*` then we currently panic, but panicking is bad! Instead let's thread through structured errors to make sure they make their way to the top 2018-09-22 03:29:50 +03:00			error: setters must start with `set_`, found: a
Update UI tests 2019-01-02 19:35:01 +03:00			`--> $DIR/invalid-setter.rs:12:8`
Improve error message for `infer_setter_property` If the setter doesn't start with `set_*` then we currently panic, but panicking is bad! Instead let's thread through structured errors to make sure they make their way to the top 2018-09-22 03:29:50 +03:00			`\|`
Update UI tests 2019-01-02 19:35:01 +03:00			`12 \| fn a(this: &A, b: i32);`
Improve error message for `infer_setter_property` If the setter doesn't start with `set_*` then we currently panic, but panicking is bad! Instead let's thread through structured errors to make sure they make their way to the top 2018-09-22 03:29:50 +03:00			`\| ^`

Support `#[wasm_bindgen(setter, js_name = ...)]` Previously we'd require the explicit `js_name` to also start with `set_`, but when explicitly specified it shouldn't be mangled at all! Closes #584 2018-09-22 03:34:41 +03:00			`error: aborting due to previous error`
Improve error message for `infer_setter_property` If the setter doesn't start with `set_*` then we currently panic, but panicking is bad! Instead let's thread through structured errors to make sure they make their way to the top 2018-09-22 03:29:50 +03:00