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

Tracking issue for RFC 1868: A portability lint #41619

aturon opened this Issue Apr 29, 2017 · 3 comments


None yet
5 participants

aturon commented Apr 29, 2017

This is a tracking issue for the RFC "A portability lint" (rust-lang/rfcs#1868).


Unresolved questions:

  • It's not clear what the story should be for a library like libc, which currently involves intricate uses of cfg. We should have some idea for how to approach such cases before landing the RFC.

This comment has been minimized.


durka commented Jul 8, 2017

cc #43086


This comment has been minimized.


SimonSapin commented Jul 8, 2017

When this is implemented, reconsider ExactSizeIterator for Range<_> and RangeInclusive<_>: #43086 (comment)


This comment has been minimized.


eternaleye commented Jul 20, 2018

Just encountered a relevant research project - their work may have aspects we can reuse:

TypeChef is a research project with the goal of analyzing ifdef variability in C code with the goal of finding variability-induced bugs in large-scale real-world systems, such as the Linux kernel with several thousand features (or configuration options).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment