Skip to content

Commit 134ca0b

Browse files
committed
fix misattribution
1 parent d4d6e38 commit 134ca0b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

text/0000-union-initialization-and-drop.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -324,8 +324,8 @@ can be pretty hard for the programmer to predict when drop glue will be
324324
automatically invoked on assignment or not, because the initialization tracking
325325
(which this RFC adapts from @petrochenkov's proposal) can sometimes be a little
326326
surprising when looking at individual fields: Whether `u.f2 = ...;` drops
327-
depends on whether `u.f1` has been previously initialized. @petrochenkov hence
328-
proposes a lint to warn people that unions with drop-glue fields are not always
327+
depends on whether `u.f1` has been previously initialized. We hence
328+
have a lint to warn people that unions with drop-glue fields are not always
329329
very well-behaved. This RFC, on the other hand, side-steps the entire question
330330
by not allowing fields with drop glue. Initialization tracking thus has no
331331
effect on the code executed during an assignment of a union field. For unions

0 commit comments

Comments
 (0)