Brian Anderson 29e0235415 Add a platform-abstraction tidy script ...

This is intended to maintain existing standards of code organization
in hopes that the standard library will continue to be refactored to
isolate platform-specific bits, making porting easier; where "standard
library" roughly means "all the dependencies of the std and test
crates".

This generally means placing restrictions on where `cfg(unix)`,
`cfg(windows)`, `cfg(target_os)` and `cfg(target_env)` may appear,
the basic objective being to isolate platform-specific code to the
platform-specific `std::sys` modules, and to the allocation,
unwinding, and libc crates.

Following are the basic rules, though there are currently
exceptions:

- core may not have platform-specific code
- liballoc_system may have platform-specific code
- liballoc_jemalloc may have platform-specific code
- libpanic_abort may have platform-specific code
- libpanic_unwind may have platform-specific code
- other crates in the std facade may not
- std may have platform-specific code in the following places
  - sys/unix/
  - sys/windows/
  - os/

There are plenty of exceptions today though, noted in the whitelist.

2016-10-02 14:52:15 -07:00

..

addr.rs

Ignore various entire test modules on emscripten

2016-09-30 14:02:56 -07:00

ip.rs

Ignore entire test modules on emscripten instead of individual tests

2016-09-30 14:02:52 -07:00

mod.rs

Add a platform-abstraction tidy script

2016-10-02 14:52:15 -07:00

parser.rs

Add missing Eq implementations

2016-09-18 14:26:49 +02:00

tcp.rs

Ignore entire test modules on emscripten instead of individual tests

2016-09-30 14:02:52 -07:00

test.rs

Add a platform-abstraction tidy script

2016-10-02 14:52:15 -07:00

udp.rs

Ignore entire test modules on emscripten instead of individual tests

2016-09-30 14:02:52 -07:00