Skip to content

Commit eca25f7

Browse files
Add more mixing packed and aligned to future possibilities
1 parent 3a4f5ac commit eca25f7

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

text/3806-align-attr.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -363,7 +363,6 @@ fn foo(x: &u8) {
363363
2. Does MSVC do something weird with `alignas`? In other words, is the concern
364364
about `repr(C)` vs `repr(linear)` purely theoretical at this point, or does
365365
it matter in practice today?
366-
367366
# Future possibilities
368367
[future-possibilities]: #future-possibilities
369368

@@ -375,3 +374,6 @@ fn foo(x: &u8) {
375374
- We could add type-safe APIs for over-aligned pointers; for example,
376375
over-aligned reference types that are subtypes of `&`/`&mut`.
377376
- We could also add similar APIs for over-aligned function pointers.
377+
- We could loosen the restriction that fields of a `packed(n)` struct cannot
378+
specify an alignment greater that `n`. (Apparently, some C compilers allow
379+
something similar.)

0 commit comments

Comments
 (0)