From e0418bf4b93a3ed595cc59eab994330fefdaab7b Mon Sep 17 00:00:00 2001 From: Ahmed Ibrahim Date: Fri, 22 Aug 2025 20:08:51 -0700 Subject: [PATCH] rust --- codex-rs/tui/tests/fixtures/ideal-binary-response.txt | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/codex-rs/tui/tests/fixtures/ideal-binary-response.txt b/codex-rs/tui/tests/fixtures/ideal-binary-response.txt index 89da1aa7db..56ed4a46a7 100644 --- a/codex-rs/tui/tests/fixtures/ideal-binary-response.txt +++ b/codex-rs/tui/tests/fixtures/ideal-binary-response.txt @@ -9,8 +9,7 @@ codex I’m going to scan the workspace and Cargo manifests to see build profiles and dependencies that impact binary size. Then I’ll summarize the main causes. - ->_ +_ ✓ ls -la └ total 6696 drwxr-xr-x@ 39 easong staff 1248 Aug 9 08:49 . @@ -32,7 +31,6 @@ dependencies that impact binary size. Then I’ll summarize the main causes. … +38 lines codegen-units = 1 - [patch.crates-io] # ratatui = { path = "../../ratatui" } ratatui = { git = "https://github.com/nornagon/ratatui", branch = @@ -57,7 +55,6 @@ echo "--- $d/Cargo.toml"; sed -n '1,200p' $d/Cargo.toml; echo; done version = { workspace = true } edition = "2024" - … +23 lines serde_json = "1.0.142" serde_with = { version = "3", features = ["macros"] } @@ -208,4 +205,4 @@ assertions—outputs are much larger than cargo build --release. If you want, I can outline targeted trims (e.g., strip = "debuginfo", opt-level = "z", panic abort, tighter tokio/reqwest features) and estimate impact per -binary. +binary. \ No newline at end of file