Skip to content

Commit 4852200

Browse files
David WoodHavvy
authored andcommitted
Change / to or in wording.
Co-Authored-By: Ryan Scheel <[email protected]>
1 parent b6f0ecb commit 4852200

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/attributes/diagnostics.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -255,7 +255,7 @@ When used on a function in a trait implementation, the attribute does nothing.
255255
# The `non_exhaustive` attribute
256256
257257
The *`non_exhaustive` attribute* is used to indicate that a type will have
258-
more fields/variants added in the future. It can be applied to
258+
more fields or variants added in the future. It can be applied to
259259
[`struct`s][struct], [`enum`s][enum] and `enum` variants.
260260
261261
The `non_exhaustive` attribute uses the [_MetaWord_] syntax and thus does not
@@ -306,7 +306,7 @@ match message {
306306
```
307307
308308
In downstream crates, types annotated with `non_exhaustive` have limitations that
309-
preserve backwards compatibility when new fields/variants are added.
309+
preserve backwards compatibility when new fields or variants are added.
310310

311311
Non-exhaustive types cannot be constructed in downstream crates:
312312

@@ -335,7 +335,7 @@ let message = Message::Reaction(0);
335335
let message = Message::Quit;
336336
```
337337

338-
Non-exhaustive types cannot be used in a [`match`]/[`if let`] expression without a
338+
Non-exhaustive types cannot be used in a [`match`] or [`if let`] expression without a
339339
wildcard arm:
340340

341341
```rust, ignore

0 commit comments

Comments
 (0)