[tor-commits] [tor/release-0.3.5] Remove `[features]` from workspace Cargo.toml

[nickm@xxxxxxxxxxxxxx]

commit 757a2360a41a5de2abd283ddee9fd26bb045bc04
Author: Alex Crichton <alex@xxxxxxxxxxxxxxxx>
Date:   Mon Oct 1 22:57:38 2018 -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...
---
 src/rust/Cargo.toml | 16 ----------------
 1 file changed, 16 deletions(-)

diff --git a/src/rust/Cargo.toml b/src/rust/Cargo.toml
index e399dbb33..83f962966 100644
--- 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 = []



_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits