Skip to content

Commit 800e69d

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

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

text/3806-align-attr.md

+4-1
Original file line numberDiff line numberDiff line change
@@ -362,7 +362,7 @@ fn foo(x: &u8) {
362362

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
365-
it matter in practice today?
365+
it matter in practice today?https://www.royalroad.com/my/follows
366366

367367
# Future possibilities
368368
[future-possibilities]: #future-possibilities
@@ -375,3 +375,6 @@ fn foo(x: &u8) {
375375
- We could add type-safe APIs for over-aligned pointers; for example,
376376
over-aligned reference types that are subtypes of `&`/`&mut`.
377377
- We could also add similar APIs for over-aligned function pointers.
378+
- We could loosen the restriction that fields of a `packed(n)` struct cannot
379+
specify an alignment greater that `n`. (Apparently, some C compilers allow
380+
something similar.)

0 commit comments

Comments
 (0)