Force inlining source and target node id lookup in candidate hops
[rust-lightning] / Cargo.toml
index 5aa90975a3a71160c99387114744cf910e8c6dde..a12f6ff9ff3de2ded9fbc368029aba53f945f066 100644 (file)
@@ -1,19 +1,22 @@
 [workspace]
+resolver = "2"
 
 members = [
     "lightning",
     "lightning-block-sync",
-    "lightning-transaction-sync",
     "lightning-invoice",
     "lightning-net-tokio",
     "lightning-persister",
     "lightning-background-processor",
-    "lightning-rapid-gossip-sync"
+    "lightning-rapid-gossip-sync",
+    "lightning-custom-message",
 ]
 
 exclude = [
-    "lightning-custom-message",
+    "lightning-transaction-sync",
     "no-std-check",
+    "msrv-no-dev-deps-check",
+    "bench",
 ]
 
 # Our tests do actual crypto and lots of work, the tradeoff for -O2 is well
@@ -35,8 +38,3 @@ lto = "off"
 opt-level = 3
 lto = true
 panic = "abort"
-
-[profile.bench]
-opt-level = 3
-codegen-units = 1
-lto = true