File tree Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Original file line number Diff line number Diff line change 119
119
//
120
120
// Finally, a leading “v” in the pattern indicates that the reports will be shown
121
121
// to the user of bisect to describe the changes involved in a failure.
122
- // At the API level, the leading “v” causes [Matcher.Visible ] to return true.
122
+ // At the API level, the leading “v” causes [Matcher.Verbose ] to return true.
123
123
// See the next section for details.
124
124
//
125
125
// # Match Reports
136
136
// 0x1234 is the change ID in hexadecimal.
137
137
// An alternate form is “[bisect-match 010101]”, giving the change ID in binary.
138
138
//
139
- // When [Matcher.Visible ] returns false, the match reports are only
139
+ // When [Matcher.Verbose ] returns false, the match reports are only
140
140
// being processed by bisect to learn the set of enabled changes,
141
141
// not shown to the user, meaning that each report can be a match
142
142
// marker on a line by itself, eliding the usual textual description.
143
143
// When the textual description is expensive to compute,
144
- // checking [Matcher.Visible ] can help the avoid that expense
144
+ // checking [Matcher.Verbose ] can help the avoid that expense
145
145
// in most runs.
146
146
package bisect
147
147
You can’t perform that action at this time.
0 commit comments