Skip to content

Commit a90e903

Browse files
Fix markdown formatting in opaque-apis.md
The current bare "<T>" seems to be interpreted as an unknown HTML tag by markdown parsers, which renders it invisible. Wrapping it in backticks seems to fix this. PiperOrigin-RevId: 1015541567
1 parent 9acf406 commit a90e903

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

‎content/design-decisions/opaque-apis.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -83,9 +83,9 @@ because the presence bit is not reachable from the field expression itself. The
8383
typical representation ends up being a pointer per field — `*int32`, `*bool`,
8484
`java.lang.Integer` — which costs a machine word in the parent struct, a
8585
separate allocation, an extra indirection on every read, and garbage collector
86-
pressure, all to carry one bit. Even in languages like Rust with Option<T>, the
87-
Open API precludes maintaining a dense hasbit bitmask over all of the fields,
88-
and instead spreads out the option bit throughout the struct (including
86+
pressure, all to carry one bit. Even in languages like Rust with `Option<T>`,
87+
the Open API precludes maintaining a dense hasbit bitmask over all of the
88+
fields, and instead spreads out the option bit throughout the struct (including
8989
typically with a lot of wasting padding per field).
9090

9191
Dense hasbits are not just cheaper to store; they make whole-message operations

0 commit comments

Comments
 (0)