-
Notifications
You must be signed in to change notification settings - Fork 190
Skip update fallback if return type has non-static lifetime #896
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from 3 commits
f2fbc8e
38e20bb
9364f15
d812631
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -494,6 +494,7 @@ fallback_impl! { compact_str::CompactString, } | |
|
|
||
| macro_rules! tuple_impl { | ||
| ($($t:ident),*; $($u:ident),*) => { | ||
| #[diagnostic::do_not_recommend] | ||
|
||
| unsafe impl<$($t),*> Update for ($($t,)*) | ||
| where | ||
| $($t: Update,)* | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,27 @@ | ||
| //! Test that a `tracked` function can return a | ||
| //! non-`Update` type, so long as it has `'static` lifetime. | ||
|
|
||
| use salsa::Database; | ||
|
|
||
| #[salsa::input] | ||
| struct Input {} | ||
|
|
||
| #[derive(Clone, PartialEq)] | ||
| struct NotUpdate<'a> { | ||
| _marker: std::marker::PhantomData<&'a ()>, | ||
| } | ||
|
|
||
| #[salsa::tracked] | ||
| fn test(_db: &dyn salsa::Database, _: Input) -> NotUpdate<'static> { | ||
| NotUpdate { | ||
| _marker: std::marker::PhantomData, | ||
| } | ||
| } | ||
|
|
||
| #[test] | ||
| fn invoke() { | ||
| salsa::DatabaseImpl::new().attach(|db| { | ||
| let input = Input::new(db); | ||
| test(db, input); | ||
| }) | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This unfortunately breaks down with macro calls in the type,
-> foo!()might expand to something introducing an elided lifetime. Likewise a user could use aFoo<'_>but without specifying the<'_>which warns post 2018 edition, but not error.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Both of those seem like reasonable gaps to me, since it will still fallback to the current behaviour. Although I could see the argument that it might create even more confusing behaviour.
What do you think the best path forward is? I have no problems with closing this PR if it doesn't seem worth it.