You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: tests/ui/feature-gates/feature-gate-precise_pointer_size_matching.stderr
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ LL | match 0usize {
5
5
| ^^^^^^ pattern `usize::MAX..` not covered
6
6
|
7
7
= note: the matched value is of type `usize`
8
-
= note: `usize` does not have a fixed maximum value, so half-open ranges are necessary to match exhaustively
8
+
= note: `usize::MAX` is not treated as exhaustive, so half-open ranges are necessary to match exhaustively
9
9
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
10
10
|
11
11
LL ~ 0..=usize::MAX => {},
@@ -19,7 +19,7 @@ LL | match 0isize {
19
19
| ^^^^^^ patterns `..isize::MIN` and `isize::MAX..` not covered
20
20
|
21
21
= note: the matched value is of type `isize`
22
-
= note: `isize` does not have fixed minimum and maximum values, so half-open ranges are necessary to match exhaustively
22
+
= note: `isize::MIN` and `isize::MAX` are not treated as exhaustive, so half-open ranges are necessary to match exhaustively
23
23
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern, a match arm with multiple or-patterns as shown, or multiple match arms
Copy file name to clipboardExpand all lines: tests/ui/pattern/usefulness/integer-ranges/pointer-sized-int.deny.stderr
+11-11Lines changed: 11 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ LL | match 0usize {
5
5
| ^^^^^^ pattern `usize::MAX..` not covered
6
6
|
7
7
= note: the matched value is of type `usize`
8
-
= note: `usize` does not have a fixed maximum value, so half-open ranges are necessary to match exhaustively
8
+
= note: `usize::MAX` is not treated as exhaustive, so half-open ranges are necessary to match exhaustively
9
9
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
10
10
|
11
11
LL ~ 0..=usize::MAX => {},
@@ -19,7 +19,7 @@ LL | match 0isize {
19
19
| ^^^^^^ patterns `..isize::MIN` and `isize::MAX..` not covered
20
20
|
21
21
= note: the matched value is of type `isize`
22
-
= note: `isize` does not have fixed minimum and maximum values, so half-open ranges are necessary to match exhaustively
22
+
= note: `isize::MIN` and `isize::MAX` are not treated as exhaustive, so half-open ranges are necessary to match exhaustively
23
23
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern, a match arm with multiple or-patterns as shown, or multiple match arms
| ^^^^^^ patterns `..isize::MIN` and `isize::MAX..` not covered
86
86
|
87
87
= note: the matched value is of type `isize`
88
-
= note: `isize` does not have fixed minimum and maximum values, so half-open ranges are necessary to match exhaustively
88
+
= note: `isize::MIN` and `isize::MAX` are not treated as exhaustive, so half-open ranges are necessary to match exhaustively
89
89
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern, a match arm with multiple or-patterns as shown, or multiple match arms
| ^^^^^^ patterns `..isize::MIN` and `isize::MAX..` not covered
99
99
|
100
100
= note: the matched value is of type `isize`
101
-
= note: `isize` does not have fixed minimum and maximum values, so half-open ranges are necessary to match exhaustively
101
+
= note: `isize::MIN` and `isize::MAX` are not treated as exhaustive, so half-open ranges are necessary to match exhaustively
102
102
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern, a match arm with multiple or-patterns as shown, or multiple match arms
| ^^^^^^ patterns `..isize::MIN` and `isize::MAX..` not covered
112
112
|
113
113
= note: the matched value is of type `isize`
114
-
= note: `isize` does not have fixed minimum and maximum values, so half-open ranges are necessary to match exhaustively
114
+
= note: `isize::MIN` and `isize::MAX` are not treated as exhaustive, so half-open ranges are necessary to match exhaustively
115
115
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern, a match arm with multiple or-patterns as shown, or multiple match arms
| ^^^^^^ patterns `..isize::MIN` and `isize::MAX..` not covered
125
125
|
126
126
= note: the matched value is of type `isize`
127
-
= note: `isize` does not have fixed minimum and maximum values, so half-open ranges are necessary to match exhaustively
127
+
= note: `isize::MIN` and `isize::MAX` are not treated as exhaustive, so half-open ranges are necessary to match exhaustively
128
128
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern, a match arm with multiple or-patterns as shown, or multiple match arms
| ^^^^^^^^^^^^^^ patterns `(..isize::MIN, _)` and `(isize::MAX.., _)` not covered
138
138
|
139
139
= note: the matched value is of type `(isize, bool)`
140
-
= note: `isize` does not have fixed minimum and maximum values, so half-open ranges are necessary to match exhaustively
140
+
= note: `isize::MIN` and `isize::MAX` are not treated as exhaustive, so half-open ranges are necessary to match exhaustively
141
141
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern, a match arm with multiple or-patterns as shown, or multiple match arms
Copy file name to clipboardExpand all lines: tests/ui/pattern/usefulness/integer-ranges/precise_pointer_matching-message.stderr
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ LL | match 0usize {
5
5
| ^^^^^^ pattern `usize::MAX..` not covered
6
6
|
7
7
= note: the matched value is of type `usize`
8
-
= note: `usize` does not have a fixed maximum value, so half-open ranges are necessary to match exhaustively
8
+
= note: `usize::MAX` is not treated as exhaustive, so half-open ranges are necessary to match exhaustively
9
9
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
10
10
|
11
11
LL ~ 0..=usize::MAX => {},
@@ -19,7 +19,7 @@ LL | match 0isize {
19
19
| ^^^^^^ patterns `..isize::MIN` and `isize::MAX..` not covered
20
20
|
21
21
= note: the matched value is of type `isize`
22
-
= note: `isize` does not have fixed minimum and maximum values, so half-open ranges are necessary to match exhaustively
22
+
= note: `isize::MIN` and `isize::MAX` are not treated as exhaustive, so half-open ranges are necessary to match exhaustively
23
23
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern, a match arm with multiple or-patterns as shown, or multiple match arms
Copy file name to clipboardExpand all lines: tests/ui/pattern/usefulness/issue-85222-types-containing-non-exhaustive-types.stderr
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ LL | match 0 {
5
5
| ^ pattern `usize::MAX..` not covered
6
6
|
7
7
= note: the matched value is of type `usize`
8
-
= note: `usize` does not have a fixed maximum value, so half-open ranges are necessary to match exhaustively
8
+
= note: `usize::MAX` is not treated as exhaustive, so half-open ranges are necessary to match exhaustively
9
9
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
10
10
|
11
11
LL ~ 1..=usize::MAX => (),
@@ -19,7 +19,7 @@ LL | match (0usize, 0usize) {
19
19
| ^^^^^^^^^^^^^^^^ pattern `(usize::MAX.., _)` not covered
20
20
|
21
21
= note: the matched value is of type `(usize, usize)`
22
-
= note: `usize` does not have a fixed maximum value, so half-open ranges are necessary to match exhaustively
22
+
= note: `usize::MAX` is not treated as exhaustive, so half-open ranges are necessary to match exhaustively
23
23
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
24
24
|
25
25
LL ~ (1..=usize::MAX, 1..=usize::MAX) => (),
@@ -33,7 +33,7 @@ LL | match (0isize, 0usize) {
33
33
| ^^^^^^^^^^^^^^^^ patterns `(..isize::MIN, _)` and `(isize::MAX.., _)` not covered
34
34
|
35
35
= note: the matched value is of type `(isize, usize)`
36
-
= note: `isize` does not have fixed minimum and maximum values, so half-open ranges are necessary to match exhaustively
36
+
= note: `isize::MIN` and `isize::MAX` are not treated as exhaustive, so half-open ranges are necessary to match exhaustively
37
37
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern, a match arm with multiple or-patterns as shown, or multiple match arms
@@ -70,7 +70,7 @@ note: `Option<usize>` defined here
70
70
|
71
71
= note: not covered
72
72
= note: the matched value is of type `Option<usize>`
73
-
= note: `usize` does not have a fixed maximum value, so half-open ranges are necessary to match exhaustively
73
+
= note: `usize::MAX` is not treated as exhaustive, so half-open ranges are necessary to match exhaustively
74
74
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
75
75
|
76
76
LL ~ None => (),
@@ -93,7 +93,7 @@ note: `Option<Option<Option<usize>>>` defined here
93
93
|
94
94
= note: not covered
95
95
= note: the matched value is of type `Option<Option<Option<usize>>>`
96
-
= note: `usize` does not have a fixed maximum value, so half-open ranges are necessary to match exhaustively
96
+
= note: `usize::MAX` is not treated as exhaustive, so half-open ranges are necessary to match exhaustively
97
97
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
98
98
|
99
99
LL ~ None => (),
@@ -112,7 +112,7 @@ note: `A<usize>` defined here
112
112
LL | struct A<T> {
113
113
| ^
114
114
= note: the matched value is of type `A<usize>`
115
-
= note: `usize` does not have a fixed maximum value, so half-open ranges are necessary to match exhaustively
115
+
= note: `usize::MAX` is not treated as exhaustive, so half-open ranges are necessary to match exhaustively
116
116
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
117
117
|
118
118
LL ~ A { a: 1..=usize::MAX } => (),
@@ -131,7 +131,7 @@ note: `B<isize, usize>` defined here
131
131
LL | struct B<T, U>(T, U);
132
132
| ^
133
133
= note: the matched value is of type `B<isize, usize>`
134
-
= note: `isize` does not have fixed minimum and maximum values, so half-open ranges are necessary to match exhaustively
134
+
= note: `isize::MIN` and `isize::MAX` are not treated as exhaustive, so half-open ranges are necessary to match exhaustively
135
135
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern, a match arm with multiple or-patterns as shown, or multiple match arms
0 commit comments