From 755f01944acff6e0628336f0c0b162f7814e6931 Mon Sep 17 00:00:00 2001
From: Justin Starry <justin.starry@icloud.com>
Date: Thu, 23 Apr 2020 23:43:12 +0800
Subject: [PATCH] Update to Rust v1.43.0

---
 .github/ISSUE_TEMPLATE/bug_report.md          |  2 +-
 yew-macro/tests/derive_props/fail.stderr      |  7 +-
 yew-macro/tests/derive_props_test.rs          |  2 +-
 yew-macro/tests/macro/html-block-fail.stderr  |  3 +
 .../html-component-fail-unimplemented.stderr  | 18 ++---
 .../tests/macro/html-component-fail.stderr    | 72 ++++++++++++++++---
 .../tests/macro/html-iterable-fail.stderr     |  7 ++
 yew-macro/tests/macro/html-list-fail.stderr   | 18 ++++-
 yew-macro/tests/macro/html-node-fail.stderr   | 20 ++++++
 yew-macro/tests/macro/html-tag-fail.stderr    | 62 ++++++++++++++--
 yew-macro/tests/macro_test.rs                 |  2 +-
 yew/src/agent.rs                              |  1 -
 yew/src/format/bincode.rs                     |  2 -
 yew/src/format/toml.rs                        |  2 -
 14 files changed, 185 insertions(+), 33 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
index e514bb02997..b63b155da0b 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -25,7 +25,7 @@ If applicable, add screenshots to help explain your problem.
 
 **Environment:**
  - Yew version [e.g. v0.10, `master`]
- - Rust version [e.g. 1.42.0]
+ - Rust version [e.g. 1.43.0]
  - Target if relevant [e.g. `wasm32-unknown-emscripten`]
  - `stdweb` / `web-sys` version [e.g. web-sys v0.3.33]
  - OS: [e.g. macos]
diff --git a/yew-macro/tests/derive_props/fail.stderr b/yew-macro/tests/derive_props/fail.stderr
index 7f9b6ecae29..48ffd3bd627 100644
--- a/yew-macro/tests/derive_props/fail.stderr
+++ b/yew-macro/tests/derive_props/fail.stderr
@@ -30,6 +30,7 @@ error[E0277]: the trait bound `t1::Value: std::default::Default` is not satisfie
   |                     ^^^^^^^^^^ the trait `std::default::Default` is not implemented for `t1::Value`
   |
   = note: required by `std::default::Default::default`
+  = note: this error originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0599]: no method named `build` found for struct `t3::PropsBuilder<t3::PropsBuilderStep_missing_required_prop_value>` in the current scope
   --> $DIR/fail.rs:35:26
@@ -68,11 +69,13 @@ error[E0618]: expected function, found `{integer}`
 77 |         #[prop_or_else(123)]
    |                        ^^^ call expression requires function
 
-error[E0061]: this function takes 1 parameter but 0 parameters were supplied
+error[E0061]: this function takes 1 argument but 0 arguments were supplied
    --> $DIR/fail.rs:97:24
     |
 97  |         #[prop_or_else(foo)]
-    |                        ^^^ expected 1 parameter
+    |                        ^^^- supplied 0 arguments
+    |                        |
+    |                        expected 1 argument
 ...
 101 |     fn foo(bar: i32) -> String {
     |     -------------------------- defined here
diff --git a/yew-macro/tests/derive_props_test.rs b/yew-macro/tests/derive_props_test.rs
index 3af86c866dd..507c1882eac 100644
--- a/yew-macro/tests/derive_props_test.rs
+++ b/yew-macro/tests/derive_props_test.rs
@@ -1,5 +1,5 @@
 #[allow(dead_code)]
-#[rustversion::attr(stable(1.42), test)]
+#[rustversion::attr(stable(1.43), test)]
 fn tests() {
     let t = trybuild::TestCases::new();
     t.pass("tests/derive_props/pass.rs");
diff --git a/yew-macro/tests/macro/html-block-fail.stderr b/yew-macro/tests/macro/html-block-fail.stderr
index 71aebfff923..c5d845d6b38 100644
--- a/yew-macro/tests/macro/html-block-fail.stderr
+++ b/yew-macro/tests/macro/html-block-fail.stderr
@@ -9,6 +9,7 @@ error[E0277]: `()` doesn't implement `std::fmt::Display`
   = note: required because of the requirements on the impl of `std::string::ToString` for `()`
   = note: required because of the requirements on the impl of `std::convert::From<()>` for `yew::virtual_dom::vnode::VNode`
   = note: required by `std::convert::From::from`
+  = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0277]: `()` doesn't implement `std::fmt::Display`
   --> $DIR/html-block-fail.rs:12:16
@@ -21,6 +22,7 @@ error[E0277]: `()` doesn't implement `std::fmt::Display`
    = note: required because of the requirements on the impl of `std::string::ToString` for `()`
    = note: required because of the requirements on the impl of `std::convert::From<()>` for `yew::virtual_dom::vnode::VNode`
    = note: required by `std::convert::From::from`
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0277]: `()` doesn't implement `std::fmt::Display`
   --> $DIR/html-block-fail.rs:15:17
@@ -33,3 +35,4 @@ error[E0277]: `()` doesn't implement `std::fmt::Display`
    = note: required because of the requirements on the impl of `std::string::ToString` for `()`
    = note: required because of the requirements on the impl of `std::convert::From<()>` for `yew::virtual_dom::vnode::VNode`
    = note: required because of the requirements on the impl of `std::convert::Into<yew::virtual_dom::vnode::VNode>` for `()`
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
diff --git a/yew-macro/tests/macro/html-component-fail-unimplemented.stderr b/yew-macro/tests/macro/html-component-fail-unimplemented.stderr
index a9187d96e00..f282af3ee95 100644
--- a/yew-macro/tests/macro/html-component-fail-unimplemented.stderr
+++ b/yew-macro/tests/macro/html-component-fail-unimplemented.stderr
@@ -1,12 +1,12 @@
 error[E0599]: no function or associated item named `new` found for struct `yew::virtual_dom::vcomp::VChild<std::string::String>` in the current scope
- --> $DIR/html-component-fail-unimplemented.rs:6:5
-  |
-6 |     html! { <String /> };
-  |     ^^^^^^^^^^^^^^^^^^^^^ function or associated item not found in `yew::virtual_dom::vcomp::VChild<std::string::String>`
-  |
-  = note: the method `new` exists but the following trait bounds were not satisfied:
-          `std::string::String : yew::html::Component`
-  = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
+   --> $DIR/html-component-fail-unimplemented.rs:6:5
+    |
+6   |       html! { <String /> };
+    |       ^^^^^^^^^^^^^^^^^^^^^ function or associated item not found in `yew::virtual_dom::vcomp::VChild<std::string::String>`
+    |
+    = note: the method `new` exists but the following trait bounds were not satisfied:
+            `std::string::String: yew::html::Component`
+    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0277]: the trait bound `std::string::String: yew::html::Component` is not satisfied
  --> $DIR/html-component-fail-unimplemented.rs:6:5
@@ -14,4 +14,4 @@ error[E0277]: the trait bound `std::string::String: yew::html::Component` is not
 6 |     html! { <String /> };
   |     ^^^^^^^^^^^^^^^^^^^^^ the trait `yew::html::Component` is not implemented for `std::string::String`
   |
-  = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
+  = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
diff --git a/yew-macro/tests/macro/html-component-fail.stderr b/yew-macro/tests/macro/html-component-fail.stderr
index d16126cc9f2..12744668add 100644
--- a/yew-macro/tests/macro/html-component-fail.stderr
+++ b/yew-macro/tests/macro/html-component-fail.stderr
@@ -3,12 +3,16 @@ error: this open tag has no corresponding close tag
    |
 79 |     html! { <Child> };
    |             ^^^^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: expected identifier
   --> $DIR/html-component-fail.rs:80:22
    |
 80 |     html! { <Child:: /> };
    |                      ^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: unexpected end of input, expected identifier
   --> $DIR/html-component-fail.rs:81:5
@@ -16,91 +20,119 @@ error: unexpected end of input, expected identifier
 81 |     html! { <Child with /> };
    |     ^^^^^^^^^^^^^^^^^^^^^^^^^
    |
-   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: unexpected token
   --> $DIR/html-component-fail.rs:82:20
    |
 82 |     html! { <Child props /> };
    |                    ^^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: this open tag has no corresponding close tag
   --> $DIR/html-component-fail.rs:83:13
    |
 83 |     html! { <Child with props > };
    |             ^^^^^^^^^^^^^^^^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: too many refs set
   --> $DIR/html-component-fail.rs:84:38
    |
 84 |     html! { <Child with props ref=() ref=() /> };
    |                                      ^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: too many refs set
   --> $DIR/html-component-fail.rs:85:38
    |
 85 |     html! { <Child with props ref=() ref=() value=1 /> };
    |                                      ^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: Using special syntax `with props` along with named prop is not allowed. This rule does not apply to special `ref` prop
   --> $DIR/html-component-fail.rs:86:38
    |
 86 |     html! { <Child with props ref=() value=1 ref=() /> };
    |                                      ^^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: Using special syntax `with props` along with named prop is not allowed. This rule does not apply to special `ref` prop
   --> $DIR/html-component-fail.rs:87:31
    |
 87 |     html! { <Child with props value=1 ref=()  ref=() /> };
    |                               ^^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: Using special syntax `with props` along with named prop is not allowed. This rule does not apply to special `ref` prop
   --> $DIR/html-component-fail.rs:88:28
    |
 88 |     html! { <Child value=1 with props  ref=()  ref=() /> };
    |                            ^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: Using special syntax `with props` along with named prop is not allowed. This rule does not apply to special `ref` prop
   --> $DIR/html-component-fail.rs:89:35
    |
 89 |     html! { <Child value=1 ref=() with props ref=() /> };
    |                                   ^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: too many refs set
   --> $DIR/html-component-fail.rs:90:27
    |
 90 |     html! { <Child ref=() ref=() value=1  with props  /> };
    |                           ^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: unexpected token
   --> $DIR/html-component-fail.rs:92:31
    |
 92 |     html! { <Child with props () /> };
    |                               ^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: Using special syntax `with props` along with named prop is not allowed. This rule does not apply to special `ref` prop
   --> $DIR/html-component-fail.rs:93:28
    |
 93 |     html! { <Child value=1 with props /> };
    |                            ^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: Using special syntax `with props` along with named prop is not allowed. This rule does not apply to special `ref` prop
   --> $DIR/html-component-fail.rs:94:31
    |
 94 |     html! { <Child with props value=1 /> };
    |                               ^^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: expected identifier
   --> $DIR/html-component-fail.rs:95:20
    |
 95 |     html! { <Child type=0 /> };
    |                    ^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: expected identifier
   --> $DIR/html-component-fail.rs:96:20
    |
 96 |     html! { <Child invalid-prop-name=0 /> };
    |                    ^^^^^^^^^^^^^^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: unexpected end of input, expected expression
   --> $DIR/html-component-fail.rs:98:5
@@ -108,49 +140,63 @@ error: unexpected end of input, expected expression
 98 |     html! { <Child string= /> };
    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
-   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: too many refs set
    --> $DIR/html-component-fail.rs:103:33
     |
 103 |     html! { <Child int=1 ref=() ref=() /> };
     |                                 ^^^
+    |
+    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: this close tag has no corresponding open tag
    --> $DIR/html-component-fail.rs:106:13
     |
 106 |     html! { </Child> };
     |             ^^^^^^^^
+    |
+    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: this open tag has no corresponding close tag
    --> $DIR/html-component-fail.rs:107:13
     |
 107 |     html! { <Child><Child></Child> };
     |             ^^^^^^^
+    |
+    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: only one root html element allowed
    --> $DIR/html-component-fail.rs:108:28
     |
 108 |     html! { <Child></Child><Child></Child> };
     |                            ^^^^^^^^^^^^^^^
+    |
+    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: this close tag has no corresponding open tag
    --> $DIR/html-component-fail.rs:117:30
     |
 117 |     html! { <Generic<String>></Generic> };
     |                              ^^^^^^^^^^
+    |
+    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: this close tag has no corresponding open tag
    --> $DIR/html-component-fail.rs:118:30
     |
 118 |     html! { <Generic<String>></Generic<Vec<String>>> };
     |                              ^^^^^^^^^^^^^^^^^^^^^^^
+    |
+    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0425]: cannot find value `blah` in this scope
   --> $DIR/html-component-fail.rs:91:25
    |
 91 |     html! { <Child with blah /> };
    |                         ^^^^ not found in this scope
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0609]: no field `unknown` on type `ChildProperties`
   --> $DIR/html-component-fail.rs:97:20
@@ -159,6 +205,7 @@ error[E0609]: no field `unknown` on type `ChildProperties`
    |                    ^^^^^^^ unknown field
    |
    = note: available fields are: `string`, `int`
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0599]: no method named `unknown` found for struct `ChildPropertiesBuilder<ChildPropertiesBuilderStep_missing_required_prop_int>` in the current scope
   --> $DIR/html-component-fail.rs:97:20
@@ -168,6 +215,8 @@ error[E0599]: no method named `unknown` found for struct `ChildPropertiesBuilder
 ...
 97 |     html! { <Child unknown="unknown" /> };
    |                    ^^^^^^^ method not found in `ChildPropertiesBuilder<ChildPropertiesBuilderStep_missing_required_prop_int>`
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0277]: the trait bound `yew::virtual_dom::vcomp::VComp: yew::virtual_dom::Transformer<(), std::string::String>` is not satisfied
   --> $DIR/html-component-fail.rs:99:33
@@ -182,6 +231,7 @@ error[E0277]: the trait bound `yew::virtual_dom::vcomp::VComp: yew::virtual_dom:
              <yew::virtual_dom::vcomp::VComp as yew::virtual_dom::Transformer<&'a str, std::string::String>>
            and 3 others
    = note: required by `yew::virtual_dom::Transformer::transform`
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0277]: the trait bound `yew::virtual_dom::vcomp::VComp: yew::virtual_dom::Transformer<{integer}, std::string::String>` is not satisfied
    --> $DIR/html-component-fail.rs:100:33
@@ -196,6 +246,7 @@ error[E0277]: the trait bound `yew::virtual_dom::vcomp::VComp: yew::virtual_dom:
               <yew::virtual_dom::vcomp::VComp as yew::virtual_dom::Transformer<&'a str, std::string::String>>
             and 3 others
     = note: required by `yew::virtual_dom::Transformer::transform`
+    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0277]: the trait bound `yew::virtual_dom::vcomp::VComp: yew::virtual_dom::Transformer<{integer}, std::string::String>` is not satisfied
    --> $DIR/html-component-fail.rs:101:33
@@ -210,12 +261,15 @@ error[E0277]: the trait bound `yew::virtual_dom::vcomp::VComp: yew::virtual_dom:
               <yew::virtual_dom::vcomp::VComp as yew::virtual_dom::Transformer<&'a str, std::string::String>>
             and 3 others
     = note: required by `yew::virtual_dom::Transformer::transform`
+    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0308]: mismatched types
    --> $DIR/html-component-fail.rs:102:30
     |
 102 |     html! { <Child int=1 ref=() /> };
     |                              ^^ expected struct `yew::html::NodeRef`, found `()`
+    |
+    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0277]: the trait bound `yew::virtual_dom::vcomp::VComp: yew::virtual_dom::Transformer<u32, i32>` is not satisfied
    --> $DIR/html-component-fail.rs:104:24
@@ -230,6 +284,7 @@ error[E0277]: the trait bound `yew::virtual_dom::vcomp::VComp: yew::virtual_dom:
               <yew::virtual_dom::vcomp::VComp as yew::virtual_dom::Transformer<&'a str, std::string::String>>
             and 3 others
     = note: required by `yew::virtual_dom::Transformer::transform`
+    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0599]: no method named `string` found for struct `ChildPropertiesBuilder<ChildPropertiesBuilderStep_missing_required_prop_int>` in the current scope
    --> $DIR/html-component-fail.rs:105:20
@@ -243,6 +298,7 @@ error[E0599]: no method named `string` found for struct `ChildPropertiesBuilder<
     = help: items from traits can only be used if the trait is implemented and in scope
     = note: the following trait defines an item `string`, perhaps you need to implement it:
             candidate #1: `proc_macro::bridge::server::Literal`
+    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0599]: no method named `children` found for struct `ChildPropertiesBuilder<ChildPropertiesBuilderStep_missing_required_prop_int>` in the current scope
    --> $DIR/html-component-fail.rs:109:5
@@ -253,7 +309,7 @@ error[E0599]: no method named `children` found for struct `ChildPropertiesBuilde
 109 |     html! { <Child>{ "Not allowed" }</Child> };
     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ method not found in `ChildPropertiesBuilder<ChildPropertiesBuilderStep_missing_required_prop_int>`
     |
-    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
+    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0599]: no method named `build` found for struct `ChildContainerPropertiesBuilder<ChildContainerPropertiesBuilderStep_missing_required_prop_children>` in the current scope
    --> $DIR/html-component-fail.rs:111:5
@@ -267,7 +323,7 @@ error[E0599]: no method named `build` found for struct `ChildContainerProperties
     = help: items from traits can only be used if the trait is implemented and in scope
     = note: the following trait defines an item `build`, perhaps you need to implement it:
             candidate #1: `proc_macro::bridge::server::TokenStreamBuilder`
-    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
+    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0599]: no method named `build` found for struct `ChildContainerPropertiesBuilder<ChildContainerPropertiesBuilderStep_missing_required_prop_children>` in the current scope
    --> $DIR/html-component-fail.rs:112:5
@@ -281,7 +337,7 @@ error[E0599]: no method named `build` found for struct `ChildContainerProperties
     = help: items from traits can only be used if the trait is implemented and in scope
     = note: the following trait defines an item `build`, perhaps you need to implement it:
             candidate #1: `proc_macro::bridge::server::TokenStreamBuilder`
-    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
+    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0277]: the trait bound `yew::virtual_dom::vcomp::VChild<Child>: std::convert::From<&str>` is not satisfied
    --> $DIR/html-component-fail.rs:113:5
@@ -291,7 +347,7 @@ error[E0277]: the trait bound `yew::virtual_dom::vcomp::VChild<Child>: std::conv
     |
     = note: required because of the requirements on the impl of `std::convert::Into<yew::virtual_dom::vcomp::VChild<Child>>` for `&str`
     = note: required because of the requirements on the impl of `std::iter::IntoIterator` for `yew::utils::NodeSeq<&str, yew::virtual_dom::vcomp::VChild<Child>>`
-    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
+    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0277]: the trait bound `yew::virtual_dom::vcomp::VChild<Child>: std::convert::From<yew::virtual_dom::vnode::VNode>` is not satisfied
    --> $DIR/html-component-fail.rs:114:5
@@ -301,7 +357,7 @@ error[E0277]: the trait bound `yew::virtual_dom::vcomp::VChild<Child>: std::conv
     |
     = note: required because of the requirements on the impl of `std::convert::Into<yew::virtual_dom::vcomp::VChild<Child>>` for `yew::virtual_dom::vnode::VNode`
     = note: required because of the requirements on the impl of `std::iter::IntoIterator` for `yew::utils::NodeSeq<yew::virtual_dom::vnode::VNode, yew::virtual_dom::vcomp::VChild<Child>>`
-    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
+    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0277]: the trait bound `yew::virtual_dom::vcomp::VChild<Child>: std::convert::From<yew::virtual_dom::vnode::VNode>` is not satisfied
    --> $DIR/html-component-fail.rs:115:5
@@ -311,4 +367,4 @@ error[E0277]: the trait bound `yew::virtual_dom::vcomp::VChild<Child>: std::conv
     |
     = note: required because of the requirements on the impl of `std::convert::Into<yew::virtual_dom::vcomp::VChild<Child>>` for `yew::virtual_dom::vnode::VNode`
     = note: required because of the requirements on the impl of `std::iter::IntoIterator` for `yew::utils::NodeSeq<yew::virtual_dom::vnode::VNode, yew::virtual_dom::vcomp::VChild<Child>>`
-    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
+    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
diff --git a/yew-macro/tests/macro/html-iterable-fail.stderr b/yew-macro/tests/macro/html-iterable-fail.stderr
index 249a5a08a6b..ce71d45531c 100644
--- a/yew-macro/tests/macro/html-iterable-fail.stderr
+++ b/yew-macro/tests/macro/html-iterable-fail.stderr
@@ -3,6 +3,8 @@ error: expected expression after `for`
   |
 4 |     html! { for };
   |             ^^^
+  |
+  = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0277]: `()` is not an iterator
  --> $DIR/html-iterable-fail.rs:5:17
@@ -12,6 +14,7 @@ error[E0277]: `()` is not an iterator
   |
   = help: the trait `std::iter::Iterator` is not implemented for `()`
   = note: required by `std::iter::IntoIterator::into_iter`
+  = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0277]: `()` is not an iterator
  --> $DIR/html-iterable-fail.rs:6:17
@@ -21,6 +24,7 @@ error[E0277]: `()` is not an iterator
   |
   = help: the trait `std::iter::Iterator` is not implemented for `()`
   = note: required by `std::iter::IntoIterator::into_iter`
+  = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0277]: `()` doesn't implement `std::fmt::Display`
  --> $DIR/html-iterable-fail.rs:7:17
@@ -33,6 +37,7 @@ error[E0277]: `()` doesn't implement `std::fmt::Display`
   = note: required because of the requirements on the impl of `std::string::ToString` for `()`
   = note: required because of the requirements on the impl of `std::convert::From<()>` for `yew::virtual_dom::vnode::VNode`
   = note: required because of the requirements on the impl of `std::convert::Into<yew::virtual_dom::vnode::VNode>` for `()`
+  = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0277]: `()` doesn't implement `std::fmt::Display`
   --> $DIR/html-iterable-fail.rs:10:17
@@ -45,6 +50,7 @@ error[E0277]: `()` doesn't implement `std::fmt::Display`
    = note: required because of the requirements on the impl of `std::string::ToString` for `()`
    = note: required because of the requirements on the impl of `std::convert::From<()>` for `yew::virtual_dom::vnode::VNode`
    = note: required because of the requirements on the impl of `std::convert::Into<yew::virtual_dom::vnode::VNode>` for `()`
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0277]: `()` doesn't implement `std::fmt::Display`
   --> $DIR/html-iterable-fail.rs:13:17
@@ -58,3 +64,4 @@ error[E0277]: `()` doesn't implement `std::fmt::Display`
    = note: required because of the requirements on the impl of `std::string::ToString` for `&()`
    = note: required because of the requirements on the impl of `std::convert::From<&()>` for `yew::virtual_dom::vnode::VNode`
    = note: required because of the requirements on the impl of `std::convert::Into<yew::virtual_dom::vnode::VNode>` for `&()`
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
diff --git a/yew-macro/tests/macro/html-list-fail.stderr b/yew-macro/tests/macro/html-list-fail.stderr
index e8a46d96b1f..a3fea8a6809 100644
--- a/yew-macro/tests/macro/html-list-fail.stderr
+++ b/yew-macro/tests/macro/html-list-fail.stderr
@@ -3,42 +3,56 @@ error: this open tag has no corresponding close tag
   |
 4 |     html! { <> };
   |             ^^
+  |
+  = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: this close tag has no corresponding open tag
  --> $DIR/html-list-fail.rs:5:13
   |
 5 |     html! { </> };
   |             ^^^
+  |
+  = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: this open tag has no corresponding close tag
  --> $DIR/html-list-fail.rs:6:13
   |
 6 |     html! { <><> };
   |             ^^
+  |
+  = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: this close tag has no corresponding open tag
  --> $DIR/html-list-fail.rs:7:13
   |
 7 |     html! { </></> };
   |             ^^^
+  |
+  = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: this open tag has no corresponding close tag
  --> $DIR/html-list-fail.rs:8:13
   |
 8 |     html! { <><></> };
   |             ^^
+  |
+  = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: only one root html element allowed
  --> $DIR/html-list-fail.rs:9:18
   |
 9 |     html! { <></><></> };
   |                  ^^^^^
+  |
+  = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: expected valid html element
   --> $DIR/html-list-fail.rs:10:15
    |
 10 |     html! { <>invalid</> };
    |               ^^^^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: unexpected end of input, expected expression
   --> $DIR/html-list-fail.rs:11:5
@@ -46,10 +60,12 @@ error: unexpected end of input, expected expression
 11 |     html! { <key=></>}
    |     ^^^^^^^^^^^^^^^^^^
    |
-   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: this open tag has no corresponding close tag
   --> $DIR/html-list-fail.rs:12:13
    |
 12 |     html! { <key="key".to_string()>invalid</key>}
    |             ^^^^^^^^^^^^^^^^^^^^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
diff --git a/yew-macro/tests/macro/html-node-fail.stderr b/yew-macro/tests/macro/html-node-fail.stderr
index 2d93d9da1bb..9446d747a0c 100644
--- a/yew-macro/tests/macro/html-node-fail.stderr
+++ b/yew-macro/tests/macro/html-node-fail.stderr
@@ -3,54 +3,72 @@ error: only one root html element allowed
   |
 4 |     html! { "valid" "invalid" };
   |                     ^^^^^^^^^
+  |
+  = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: unexpected token
  --> $DIR/html-node-fail.rs:5:29
   |
 5 |     html! { <span>{ "valid" "invalid" }</span> };
   |                             ^^^^^^^^^
+  |
+  = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: unsupported type
   --> $DIR/html-node-fail.rs:10:14
    |
 10 |     html! {  b'a' };
    |              ^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: unsupported type
   --> $DIR/html-node-fail.rs:11:14
    |
 11 |     html! {  b"str" };
    |              ^^^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: integer literal is too large
   --> $DIR/html-node-fail.rs:12:14
    |
 12 |     html! {  1111111111111111111111111111111111111111111111111111111111111111111111111111 };
    |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: unsupported type
   --> $DIR/html-node-fail.rs:13:22
    |
 13 |     html! {  <span>{ b'a' }</span> };
    |                      ^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: unsupported type
   --> $DIR/html-node-fail.rs:14:22
    |
 14 |     html! {  <span>{ b"str" }</span> };
    |                      ^^^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: integer literal is too large
   --> $DIR/html-node-fail.rs:15:22
    |
 15 |     html! {  <span>{ 1111111111111111111111111111111111111111111111111111111111111111111111111111 }</span> };
    |                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0425]: cannot find value `invalid` in this scope
  --> $DIR/html-node-fail.rs:7:13
   |
 7 |     html! { invalid };
   |             ^^^^^^^ not found in this scope
+  |
+  = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0277]: `()` doesn't implement `std::fmt::Display`
  --> $DIR/html-node-fail.rs:6:13
@@ -63,6 +81,7 @@ error[E0277]: `()` doesn't implement `std::fmt::Display`
   = note: required because of the requirements on the impl of `std::string::ToString` for `()`
   = note: required because of the requirements on the impl of `std::convert::From<()>` for `yew::virtual_dom::vnode::VNode`
   = note: required by `std::convert::From::from`
+  = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0277]: `()` doesn't implement `std::fmt::Display`
   --> $DIR/html-node-fail.rs:19:9
@@ -75,3 +94,4 @@ error[E0277]: `()` doesn't implement `std::fmt::Display`
    = note: required because of the requirements on the impl of `std::string::ToString` for `()`
    = note: required because of the requirements on the impl of `std::convert::From<()>` for `yew::virtual_dom::vnode::VNode`
    = note: required by `std::convert::From::from`
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
diff --git a/yew-macro/tests/macro/html-tag-fail.stderr b/yew-macro/tests/macro/html-tag-fail.stderr
index a27cb4c006a..1571cb83e14 100644
--- a/yew-macro/tests/macro/html-tag-fail.stderr
+++ b/yew-macro/tests/macro/html-tag-fail.stderr
@@ -3,126 +3,168 @@ error: this open tag has no corresponding close tag
   |
 6 |     html! { <div> };
   |             ^^^^^
+  |
+  = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: this open tag has no corresponding close tag
  --> $DIR/html-tag-fail.rs:7:18
   |
 7 |     html! { <div><div> };
   |                  ^^^^^
+  |
+  = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: this close tag has no corresponding open tag
  --> $DIR/html-tag-fail.rs:8:13
   |
 8 |     html! { </div> };
   |             ^^^^^^
+  |
+  = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: this open tag has no corresponding close tag
  --> $DIR/html-tag-fail.rs:9:13
   |
 9 |     html! { <div><div></div> };
   |             ^^^^^
+  |
+  = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: only one root html element allowed
   --> $DIR/html-tag-fail.rs:10:24
    |
 10 |     html! { <div></div><div></div> };
    |                        ^^^^^^^^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: this close tag has no corresponding open tag
   --> $DIR/html-tag-fail.rs:11:18
    |
 11 |     html! { <div></span> };
    |                  ^^^^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: this close tag has no corresponding open tag
   --> $DIR/html-tag-fail.rs:12:20
    |
 12 |     html! { <tag-a></tag-b> };
    |                    ^^^^^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: this close tag has no corresponding open tag
   --> $DIR/html-tag-fail.rs:13:18
    |
 13 |     html! { <div></span></div> };
    |                  ^^^^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: only one root html element allowed
   --> $DIR/html-tag-fail.rs:14:20
    |
 14 |     html! { <img /></img> };
    |                    ^^^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: expected valid html element
   --> $DIR/html-tag-fail.rs:15:18
    |
 15 |     html! { <div>Invalid</div> };
    |                  ^^^^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: only one `attr` attribute allowed
   --> $DIR/html-tag-fail.rs:17:27
    |
 17 |     html! { <input attr=1 attr=2 /> };
    |                           ^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: only one `value` attribute allowed
   --> $DIR/html-tag-fail.rs:18:32
    |
 18 |     html! { <input value="123" value="456" /> };
    |                                ^^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: only one `kind` attribute allowed
   --> $DIR/html-tag-fail.rs:19:36
    |
 19 |     html! { <input kind="checkbox" kind="submit" /> };
    |                                    ^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: only one `checked` attribute allowed
   --> $DIR/html-tag-fail.rs:20:33
    |
 20 |     html! { <input checked=true checked=false /> };
    |                                 ^^^^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: only one `disabled` attribute allowed
   --> $DIR/html-tag-fail.rs:21:34
    |
 21 |     html! { <input disabled=true disabled=false /> };
    |                                  ^^^^^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: only one `selected` attribute allowed
   --> $DIR/html-tag-fail.rs:22:35
    |
 22 |     html! { <option selected=true selected=false /> };
    |                                   ^^^^^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: only one `class` attribute allowed
   --> $DIR/html-tag-fail.rs:23:32
    |
 23 |     html! { <div class="first" class="second" /> };
    |                                ^^^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error: only one `ref` attribute allowed
   --> $DIR/html-tag-fail.rs:38:27
    |
 38 |     html! { <input ref=() ref=() /> };
    |                           ^^^
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0308]: mismatched types
   --> $DIR/html-tag-fail.rs:25:28
    |
 25 |     html! { <input checked=1 /> };
    |                            ^ expected `bool`, found integer
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0308]: mismatched types
   --> $DIR/html-tag-fail.rs:26:29
    |
 26 |     html! { <input disabled=1 /> };
    |                             ^ expected `bool`, found integer
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0308]: mismatched types
   --> $DIR/html-tag-fail.rs:27:30
    |
 27 |     html! { <option selected=1 /> };
    |                              ^ expected `bool`, found integer
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0277]: `()` doesn't implement `std::fmt::Display`
   --> $DIR/html-tag-fail.rs:28:25
@@ -133,6 +175,7 @@ error[E0277]: `()` doesn't implement `std::fmt::Display`
    = help: the trait `std::fmt::Display` is not implemented for `()`
    = note: in format strings you may be able to use `{:?}` (or {:#?} for pretty-print) instead
    = note: required because of the requirements on the impl of `std::string::ToString` for `()`
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0277]: `()` doesn't implement `std::fmt::Display`
   --> $DIR/html-tag-fail.rs:29:26
@@ -143,6 +186,7 @@ error[E0277]: `()` doesn't implement `std::fmt::Display`
    = help: the trait `std::fmt::Display` is not implemented for `()`
    = note: in format strings you may be able to use `{:?}` (or {:#?} for pretty-print) instead
    = note: required because of the requirements on the impl of `std::string::ToString` for `()`
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0277]: the trait bound `yew::html::Href: std::convert::From<()>` is not satisfied
   --> $DIR/html-tag-fail.rs:30:21
@@ -154,6 +198,7 @@ error[E0277]: the trait bound `yew::html::Href: std::convert::From<()>` is not s
              <yew::html::Href as std::convert::From<&'a str>>
              <yew::html::Href as std::convert::From<std::string::String>>
    = note: required because of the requirements on the impl of `std::convert::Into<yew::html::Href>` for `()`
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0308]: mismatched types
   --> $DIR/html-tag-fail.rs:32:20
@@ -163,6 +208,7 @@ error[E0308]: mismatched types
    |
    = note: expected struct `yew::callback::Callback<web_sys::features::gen_MouseEvent::MouseEvent>`
                 found type `{integer}`
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0308]: mismatched types
   --> $DIR/html-tag-fail.rs:33:20
@@ -172,24 +218,30 @@ error[E0308]: mismatched types
    |
    = note: expected struct `yew::callback::Callback<web_sys::features::gen_MouseEvent::MouseEvent>`
               found struct `yew::callback::Callback<std::string::String>`
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0599]: no method named `to_string` found for struct `NotToString` in the current scope
   --> $DIR/html-tag-fail.rs:35:27
    |
 3  | struct NotToString;
-   | ------------------- method `to_string` not found for this
+   | -------------------
+   | |
+   | method `to_string` not found for this
+   | doesn't satisfy `NotToString: std::fmt::Display`
+   | doesn't satisfy `NotToString: std::string::ToString`
 ...
 35 |     html! { <input string=NotToString /> };
    |                           ^^^^^^^^^^^ method not found in `NotToString`
    |
    = note: the method `to_string` exists but the following trait bounds were not satisfied:
-           `NotToString : std::string::ToString`
-   = help: items from traits can only be used if the trait is implemented and in scope
-   = note: the following trait defines an item `to_string`, perhaps you need to implement it:
-           candidate #1: `std::string::ToString`
+           `NotToString: std::fmt::Display`
+           which is required by `NotToString: std::string::ToString`
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
 
 error[E0308]: mismatched types
   --> $DIR/html-tag-fail.rs:37:24
    |
 37 |     html! { <input ref=() /> };
    |                        ^^ expected struct `yew::html::NodeRef`, found `()`
+   |
+   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
diff --git a/yew-macro/tests/macro_test.rs b/yew-macro/tests/macro_test.rs
index bc7b4e73667..645f8c64290 100644
--- a/yew-macro/tests/macro_test.rs
+++ b/yew-macro/tests/macro_test.rs
@@ -1,5 +1,5 @@
 #[allow(dead_code)]
-#[rustversion::attr(stable(1.42), test)]
+#[rustversion::attr(stable(1.43), test)]
 fn tests() {
     let t = trybuild::TestCases::new();
 
diff --git a/yew/src/agent.rs b/yew/src/agent.rs
index 02cc7e5f551..b43fe3c6d4c 100644
--- a/yew/src/agent.rs
+++ b/yew/src/agent.rs
@@ -3,7 +3,6 @@
 use crate::callback::Callback;
 use crate::scheduler::{scheduler, Runnable, Shared};
 use anymap::{self, AnyMap};
-use bincode;
 use cfg_if::cfg_if;
 use cfg_match::cfg_match;
 use log::warn;
diff --git a/yew/src/format/bincode.rs b/yew/src/format/bincode.rs
index a828dffdf37..f154568232b 100644
--- a/yew/src/format/bincode.rs
+++ b/yew/src/format/bincode.rs
@@ -1,7 +1,5 @@
 //! Contains an implementation of Bincode serialization format.
 
-use bincode;
-
 /// A representation of a Bincode data. Use it as wrapper to
 /// set a format you want to use for conversion:
 ///
diff --git a/yew/src/format/toml.rs b/yew/src/format/toml.rs
index 99cbe04164f..44dc95f2b4e 100644
--- a/yew/src/format/toml.rs
+++ b/yew/src/format/toml.rs
@@ -1,7 +1,5 @@
 //! Contains an implementation of TOML serialization format.
 
-use toml;
-
 /// A representation of a TOML data. Use it as wrapper to
 /// set a format you want to use for conversion:
 ///