Skip to content

Why libc crate is green? #7

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

Closed
ozkriff opened this issue Jun 22, 2018 · 6 comments
Closed

Why libc crate is green? #7

ozkriff opened this issue Jun 22, 2018 · 6 comments
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@ozkriff
Copy link

ozkriff commented Jun 22, 2018

Because it uses "unsafe" only inside macros?

@anderejd
Copy link
Contributor

Good find, thank you! Needs investigation.

@anderejd anderejd added bug Something isn't working help wanted Extra attention is needed good first issue Good for newcomers labels Jun 22, 2018
@anderejd
Copy link
Contributor

@anderejd
Copy link
Contributor

The scanning needs to expand macros to detect this case. Can cargo and rustc be used to output the expanded code?

@anderejd
Copy link
Contributor

anderejd commented Jun 28, 2018

@anderejd anderejd removed the good first issue Good for newcomers label Jun 28, 2018
@anderejd
Copy link
Contributor

Looks like macro expansion requires nightly, source: https://crates.io/crates/cargo-expand

@anderejd
Copy link
Contributor

#52 makes libc and similar unsafe usage present as "?" and with the default terminal foreground color. See the changelog for 0.6.0 in the readme.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants