chore: use saturating sub with max_ttl computation (#1792)

mootz12 · web-flow · commit a5c0e4b455b8 · 2026-03-26T14:22:04.000Z
### What Use `saturating_sub` when computing `max_ttl`. ### Why Add another defense layer to potential misconfigurations, and improve consistency with math usage in the repository. Closes #1791 ### Known limitations None
diff --git a/soroban-sdk/src/storage.rs b/soroban-sdk/src/storage.rs
@@ -153,7 +153,7 @@ impl Storage {
     pub fn max_ttl(&self) -> u32 {
         let seq = self.env.ledger().sequence();
         let max = self.env.ledger().max_live_until_ledger();
-        max - seq
+        max.saturating_sub(seq)
     }
 
     /// Returns if there is a value stored for the given key in the currently

Original file line number	Diff line number	Diff line change
`@@ -153,7 +153,7 @@ impl Storage {`
`153`	`153`	`pub fn max_ttl(&self) -> u32 {`
`154`	`154`	`let seq = self.env.ledger().sequence();`
`155`	`155`	`let max = self.env.ledger().max_live_until_ledger();`
`156`		`- max - seq`
	`156`	`+ max.saturating_sub(seq)`
`157`	`157`	`}`
`158`	`158`
`159`	`159`	`/// Returns if there is a value stored for the given key in the currently`