Skip to content

Commit

Permalink
Fix typo
Browse files Browse the repository at this point in the history
  • Loading branch information
HKalbasi committed Sep 25, 2023
1 parent 1844131 commit 91e5ca3
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion book/src/call_rust_from_cpp/layout_policy.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ A normal Zngur usage requires explicitly declaring data layout information (size
by value in the C++ stack. But the layout of Rust type are not stable, and can break when changing the compiler version, using
different compiler configuration (e.g. `-Z randomize-layout`) and in different targets. This can make Zngur unusable for certain
circumstances, so Zngur supports different strategies (and all of them has their own drawback) for storing Rust things by value
in the C++ stack, called "Layout policies".
in the C++, called "Layout policies".

In fact, you should never use this mode of Zngur (and any other form of static assertion on size and align) when you don't control
the final compiler that compiles the code, since it can break for your users in an unrecoverable state if they can't change the `zng` file
Expand Down

0 comments on commit 91e5ca3

Please sign in to comment.