1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
---
source: ferritin/src/tests.rs
expression: "render_interactive_for_tests(Commands::search(\"trigger line-based truncation\"))"
---
" Search results for 'trigger line-based truncation' "
" ════════════════════════════════════════════════════════════════════════════ "
" "
" ◦ fixture-crate::TestTrait (Trait) - score: 100 (relevance: 100, "
" authority: 0) "
" │ A trait for testing extremely long documentation that exceeds line "
" │ limits. "
" │ "
" │ This trait provides a comprehensive interface for data processing "
" │ operations. It demonstrates various method signatures including mutable "
" │ references, error handling, and different return types. The trait is "
" │ designed to be flexible and extensible for different use cases in data "
" │ processing pipelines. Each method serves a specific purpose in the data "
" │ transformation workflow. The implementation should handle edge cases "
" │ gracefully and provide meaningful error messages when operations fail. "
" │ This documentation intentionally spans many lines to test the "
" │ line-based truncation when paragraph truncation doesn't apply. We want "
" │ to see how the system handles documentation that goes well beyond the "
" │ 16-line limit and should trigger line-based truncation. This continues "
" │ for several more lines to ensure we exceed the limit. Line 14 of this "
" │ very long paragraph that should be truncated. Line 15 of this extremely "
" │ verbose documentation example. Line 16 which should be the last line "
" │ shown in brief mode. Line 17 that should be hidden and show a "
" │ truncation indicator. Line 18 that definitely won't be visible in brief "
" │ mode. "
" ╰─[...] "
" "
" ◦ core::line (Macro) - score: 36 (relevance: 36, authority: 0) "
" │ Expands to the line number on which it was invoked. "
" │ "
" │ With column! and file!, these macros provide debugging information for "
" │ developers about the location within the source. "
" ╰─[...] "
" "
" ◦ std::line (Macro) - score: 36 (relevance: 36, authority: 0) "
" │ Expands to the line number on which it was invoked. "
" │ "
" │ With column! and file!, these macros provide debugging information for "
" │ developers about the location within the source. "
" ╰─[...] "
" "
" ◦ core::arch::x86::_mm_prefetch (Function) - score: 31 (relevance: 31, "
" authority: 0) "
" │ Fetch the cache line that contains address p using the given STRATEGY. "
" │ "
" │ The STRATEGY must be one of: "
" ╰─[...] "
" "
" ◦ std::arch::x86::_mm_prefetch (Function) - score: 31 (relevance: 31, "
" authority: 0) "
" │ Fetch the cache line that contains address p using the given STRATEGY. "
" │ "
" │ The STRATEGY must be one of: "
" ╰─[...] "
" "
" ◦ alloc::collections::BTreeMap (Struct) - score: 30 (relevance: 16, "
" authority: 87) "
" │ An ordered map based on a B-Tree. "
" │ "
" │ Given a key type with a total order, an ordered map stores its entries "
" │ in key order. That means that keys must be of a type that implements "
" │ the Ord trait, such that two keys can always be compared to determine "
" │ their Ordering. Examples of keys with a total order are strings with "
" │ lexicographical order, and numbers with their natural order. "
" ╰─[...] "
" "
" ◦ core::column (Macro) - score: 29 (relevance: 29, authority: 0) "
" │ Expands to the column number at which it was invoked. "
" │ "
" │ With line! and file!, these macros provide debugging information for "
" │ developers about the location within the source. "
" ╰─[...] "
" "
" ◦ std::column (Macro) - score: 29 (relevance: 29, authority: 0) "
" │ Expands to the column number at which it was invoked. "
" │ "
" │ With line! and file!, these macros provide debugging information for "
" │ developers about the location within the source. "
" ╰─[...] "
" "
" ◦ std::sync (Module) - score: 28 (relevance: 28, authority: 0) "
" │ Useful synchronization primitives. "
" ╰─[...] "
" "
" ◦ core::prelude::v1::Option::map_or_else (Function) - score: 27 "
" (relevance: 27, authority: 0) "
" │ Computes a default function result (if none), or applies a different "
" │ function to the contained value (if any). "
" ╰─[...] "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
" "
"▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂"
" ferritin - q:quit ?:help ←/→:history g:go s:search l:list c:code "