tor

commit 757a2360a41a5de2abd283ddee9fd26bb045bc04
parent 74c1e44746a7d9c810f095177af88b7dbaafd3e3
Author: Alex Crichton <alex@alexcrichton.com>
Date:   Mon,  1 Oct 2018 22:57:38 -0700

Remove `[features]` from workspace Cargo.toml

Unfortunately Cargo doesn't actually parse these! Cargo should probably
print a warning saying they're not used...

Diffstat:
M
src/rust/Cargo.toml
 | 
16
----------------

1 file changed, 0 insertions(+), 16 deletions(-)
diff --git a/src/rust/Cargo.toml b/src/rust/Cargo.toml
@@ -13,19 +13,3 @@ members = [
 [profile.release]
 debug = true
 panic = "abort"
-
-[features]
-default = []
-# If this feature is enabled, test code which calls Tor C code from Rust will
-# execute with `cargo test`.  Due to numerous linker issues (#25386), this is
-# currently disabled by default.  Crates listed here are those which, in their
-# unittests, doctests, and/or integration tests, call C code.
-test-c-from-rust = [
-    "crypto/test-c-from-rust",
-]
-
-# We have to define a feature here because doctests don't get cfg(test),
-# and we need to disable some C dependencies when running the doctests
-# because of the various linker issues.  See
-# https://github.com/rust-lang/rust/issues/45599
-test_linking_hack = []