-
Notifications
You must be signed in to change notification settings - Fork 4
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
Possible bug in lifetime checker of rustc 1.62 #17
Comments
From what I can tell, the error is in the lint that checks for valid links in documentation, not a |
@jonhoo I actually encountered such lifetime error in src/fs/mod.rs, but I cannot reproduce it for now. I will close this since it cannot be reproduced, but if I encounter it again in the future, I will capture the entire output from |
@jonhoo I finally was able to reproduce it in bug:
|
|
|
@jonhoo I was also able to reproduce that on this commit once I changed /// Creates a new, empty directory at the provided path.
pub async fn create_dir(&mut self, path: impl AsRef<Path>) -> Result<(), Error> {
async fn inner(this: &mut Fs<'_>, path: &Path) -> Result<(), Error> {
this.dir_builder().create(path).await
}
inner(self, path.as_ref()).await
} then I would get:
|
Hmmm, once I removed |
I encountered it again in commit. Once I modify
@jonhoo And once again, if I remove |
This appears that 1.62 has problem with caching build artifacts in Edit: Could this be a problem with MacOS? |
This might just be bugs in MacOS. I restarted my MacBook yesterday and it hasn't yet happened today. |
Closing this since rebooting seemed to fix the issue. |
I found that
rustc
rejects when I added this commit that changes nothing related to the error.The code where error resides worked just fine without this commit or on 1.61 or earlier.
@jonhoo Could this be a bug in the
rustc
?P.S. It failed on my MacOS M1 but succeeded in the CI... Really strange.
I also experienced
clippy
reports the lifetime error butcargo
does not even without this commit.I really have no idea what is going on.
The text was updated successfully, but these errors were encountered: