We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
1 parent 3a4f5ac commit eca25f7Copy full SHA for eca25f7
text/3806-align-attr.md
@@ -363,7 +363,6 @@ fn foo(x: &u8) {
363
2. Does MSVC do something weird with `alignas`? In other words, is the concern
364
about `repr(C)` vs `repr(linear)` purely theoretical at this point, or does
365
it matter in practice today?
366
-
367
# Future possibilities
368
[future-possibilities]: #future-possibilities
369
@@ -375,3 +374,6 @@ fn foo(x: &u8) {
375
374
- We could add type-safe APIs for over-aligned pointers; for example,
376
over-aligned reference types that are subtypes of `&`/`&mut`.
377
- We could also add similar APIs for over-aligned function pointers.
+- 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