From d932812134ff28d00a0c98791926b11d1fd2025a Mon Sep 17 00:00:00 2001
From: Aleksey Kladov <aleksey.kladov@gmail.com>
Date: Wed, 10 Feb 2021 11:26:48 +0300
Subject: Use track caller in test documentation

---
 docs/dev/architecture.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'docs/dev/architecture.md')

diff --git a/docs/dev/architecture.md b/docs/dev/architecture.md
index 01063824f..081ee5b9d 100644
--- a/docs/dev/architecture.md
+++ b/docs/dev/architecture.md
@@ -372,11 +372,11 @@ Tests which directly call various API functions are a liability, because they ma
 So most of the tests look like this:
 
 ```rust
+#[track_caller]
 fn check(input: &str, expect: expect_test::Expect) {
     // The single place that actually exercises a particular API
 }
 
-
 #[test]
 fn foo() {
     check("foo", expect![["bar"]]);
-- 
cgit v1.2.3