-
Notifications
You must be signed in to change notification settings - Fork 179
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
Open
samscott89
wants to merge
4
commits into
salsa-rs:master
Choose a base branch
from
samscott89:sam/compile-err-non-update-ref
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
f2fbc8e
Don't attempt fallback if return type has non-static lifetime
samscott89 38e20bb
Add test that statics still work
samscott89 9364f15
Use a custom test in case `&'static str` later implements Update
samscott89 d812631
Remove unsupported attribute
samscott89 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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); | ||
}) | ||
} |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.