-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
ICE: Adding explicit type to parameter in closure #46007
Comments
Specifically, it is adding the explicit lifetime |
This just bit me too, but didn't even involve an explicit lifetime. This ICEs: .iterate(|valid: &Collection<_, ((usize, String), isize)>| { whereas this does not: .iterate(|valid| { |
@raphaelcohn It looks like your two example fragments are the same. Is it possible you meant to not have the |
Yes that's likely. Whoops... A bug in a bug report isn't all that helpful...
On 12 Dec 2017 7:09 p.m., "Frank McSherry" <[email protected]> wrote:
@raphaelcohn <https://github.com/raphaelcohn> It looks like your two
example fragments are the same. Is it possible you meant to not have the :
&'resources Resource in the first example?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#46007 (comment)>,
or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABPx2RZ-qg1I9Fug9kBU1RuKwt33_5cRks5s_s9ZgaJpZM4QfOad>
.
|
Is this still a problem with the latest stable/nightly? Looks like a duplicate of #38714 (which was fixed in November 5) |
Not sure
…On 13 Dec 2017 6:52 p.m., "Ariel Ben-Yehuda" ***@***.***> wrote:
Is this still a problem with the latest stable/nightly?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#46007 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABPx2WkMHfV8SmFMJmtDfRWJ_ZSGy7HVks5tAB0JgaJpZM4QfOad>
.
|
With it looking like this was fixed, and no other comments since 2017, I'm going to close this. If you're still seeing this issue, please let me know and we can re-open! |
Changing this block of code, a private function within a private instance function:-
To this block of code (ie adding
&'resources Resource
inRef::map(resourceRef, |_resource: &'resources Resource| imageMetaData);
) causes an ICE. The previous block of code does not compile correctly (error[E0312]: lifetime of reference outlives lifetime of borrowed content...
), but does not cause a compiler ICE.Details:-
The text was updated successfully, but these errors were encountered: