-
Notifications
You must be signed in to change notification settings - Fork 287
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
chore(neon): fix clippy lints #1085
Conversation
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.
@dherman, it's awesome to get these fixed! I think a couple of the memory leak releases shouldn't panic.
Maybe a good compromise is to panic in debug mode and ignore in release mode?
Additionally, I haven't traced through, but the return false
on any error lines seem incorrect. Those should probably only return false on exception.
…view: - style: don't `assert_eq!` of `Ok(())`, just `.unwrap()` - style: capitalize no_panic error message strings - logic: don't unwrap deleting async work if we're about to fail with a more clear error anyway - logic: when returning false to propagate exceptions, only do so on PendingException; panic on other errors
Awesome changes! 🐛 🪲 🔨 |
This PR fixes the Clippy lints exposed by the awesome refactoring done in #1065.