From 6d6353539732264ab18466fdcaff958797e2512c Mon Sep 17 00:00:00 2001 From: Shahak Shama Date: Sun, 15 Mar 2026 16:42:19 +0200 Subject: [PATCH] remove track_caller sentence --- style.md | 1 - 1 file changed, 1 deletion(-) diff --git a/style.md b/style.md index 5100397c863..e3416616ea7 100644 --- a/style.md +++ b/style.md @@ -71,7 +71,6 @@ Take extra care when reviewing ai-generated code for these issues: A failure in a unit test should immediately point to the source of the issue, and the clearly display the error encountered. Moreover, it should be possible to debug a test even if the test writer is not available, for example: -- add `#[track_caller]` on test-utils which include a critical assert, so that the trace will be the callsite in the test - use `assert_eq(result, Ok())` over `assert!(result.is_ok())` --- the former will display the error, and the latter will simply say `expected True, got False`. - If you're not interested in the value, or if error type doesn't implement `PartialEq`, simply call `result.unwrap()`