From: Dominik Csapak <d.csapak@proxmox.com>
To: yew-devel@lists.proxmox.com
Subject: [PATCH yew-widget-toolkit] pwt-macros: adapt tests to newer rust version
Date: Wed, 9 Sep 2026 10:51:20 +0200 [thread overview]
Message-ID: <20260909085220.3370808-1-d.csapak@proxmox.com> (raw)
we now have rust 1.94 packaged, so the error did change slightly.
new rust version has different output
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
maybe there is a better alternative than trybuild to test these?
At least the rust-src line will change on every rust version bump..
pwt-macros/tests/builder/invalid_type.stderr | 31 +++++++++++---------
pwt-macros/tests/widget/wrong_comp.stderr | 2 +-
2 files changed, 18 insertions(+), 15 deletions(-)
diff --git a/pwt-macros/tests/builder/invalid_type.stderr b/pwt-macros/tests/builder/invalid_type.stderr
index 665f828..37bfd94 100644
--- a/pwt-macros/tests/builder/invalid_type.stderr
+++ b/pwt-macros/tests/builder/invalid_type.stderr
@@ -1,19 +1,22 @@
error[E0308]: mismatched types
--> tests/builder/invalid_type.rs:5:27
|
-5 | #[builder(Into, into, 0.0)]
- | ------- ^^^ expected `i32`, found floating-point number
- | |
- | arguments to this method are incorrect
- |
+ 5 | #[builder(Into, into, 0.0)]
+ | ------- ^^^ expected `i32`, found floating-point number
+ | |
+ | arguments to this method are incorrect
+ |
help: the return type of this call is `{float}` due to the type of the argument passed
- --> tests/builder/invalid_type.rs:5:7
- |
-5 | #[builder(Into, into, 0.0)]
- | ^ --- this argument influences the return type of `unwrap_or`
- | _______|
- | |
-6 | | wrong_type: i32,
- | |______________^
+ --> tests/builder/invalid_type.rs:5:7
+ |
+ 5 | #[builder(Into, into, 0.0)]
+ | ^ --- this argument influences the return type of `unwrap_or`
+ | _______|
+ | |
+ 6 | | wrong_type: i32,
+ | |______________^
note: method defined here
- --> /usr/src/rustc-1.90.0/library/core/src/option.rs:1031:18
+ --> /usr/src/rustc-1.94.1/library/core/src/option.rs:1038:18
+ |
+1038 | pub const fn unwrap_or(self, default: T) -> T
+ | ^^^^^^^^^
diff --git a/pwt-macros/tests/widget/wrong_comp.stderr b/pwt-macros/tests/widget/wrong_comp.stderr
index c33f554..5ad771c 100644
--- a/pwt-macros/tests/widget/wrong_comp.stderr
+++ b/pwt-macros/tests/widget/wrong_comp.stderr
@@ -1,4 +1,4 @@
-error[E0412]: cannot find type `Wrong` in this scope
+error[E0425]: cannot find type `Wrong` in this scope
--> tests/widget/wrong_comp.rs:53:26
|
53 | #[widget(pwt=crate, comp=Wrong, @input, @element)]
--
2.47.3
reply other threads:[~2026-09-09 8:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260909085220.3370808-1-d.csapak@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=yew-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox