Skip to content
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

lint panics (allow) #668

Closed
llogiq opened this issue Feb 14, 2016 · 2 comments
Closed

lint panics (allow) #668

llogiq opened this issue Feb 14, 2016 · 2 comments
Labels
A-lint Area: New lints E-medium Call for participation: Medium difficulty level problem and requires some initial experience. T-middle Type: Probably requires verifiying types

Comments

@llogiq
Copy link
Contributor

llogiq commented Feb 14, 2016

We may want to know if some code is panic-free – so while we cannot be sure if a function from another crate that this crate calls panics, we can at least check for panics locally, which means checking for calls of divergent functions (which the type system should give us a hint). We also should probably ignore unreachable!() calls.

@llogiq llogiq added E-medium Call for participation: Medium difficulty level problem and requires some initial experience. T-middle Type: Probably requires verifiying types A-lint Area: New lints labels Feb 14, 2016
@basil-cow
Copy link
Contributor

This issue can now be closed, this lint was (recently?) implemented.

@flip1995
Copy link
Member

Yeah, for every directly panicking macro a separate lint is implemented by know. Thanks for noticing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-lint Area: New lints E-medium Call for participation: Medium difficulty level problem and requires some initial experience. T-middle Type: Probably requires verifiying types
Projects
None yet
Development

No branches or pull requests

3 participants