Deploying to gh-pages from @ 9452ba1 🚀

print.html

@@ -1408,6 +1408,10 @@ <h2><a class="header" href="#bitfield-strategy-overview" id="bitfield-strategy-o
 <li>For each contiguous block of bitfields, Bindgen emits an opaque physical field that contains one or more logical bitfields</li>
 <li>A static constructor  <code>new_bitfield_{1, 2, ...}</code> with a parameter for each bitfield contained within the opaque physical field.</li>
 </ul>
+<p>To keep bindgen from generating the bitfield unit struct, it can be blocklisted like any
+other type, i.e. <code>--blocklist-type &quot;__BindgenBitfieldUnit&quot;</code>. This may be useful if
+you want to define a custom implementation, or your generated bindings import a
+pre-existing definition for the bitfield unit type.</p>
 <h2><a class="header" href="#bitfield-examples" id="bitfield-examples">Bitfield examples</a></h2>
 <p>For this discussion, we will use the following C type definitions and functions.</p>
 <pre><code class="language-c">typedef struct {

using-bitfields.html

@@ -176,6 +176,10 @@ <h2><a class="header" href="#bitfield-strategy-overview" id="bitfield-strategy-o
 <li>For each contiguous block of bitfields, Bindgen emits an opaque physical field that contains one or more logical bitfields</li>
 <li>A static constructor  <code>new_bitfield_{1, 2, ...}</code> with a parameter for each bitfield contained within the opaque physical field.</li>
 </ul>
+<p>To keep bindgen from generating the bitfield unit struct, it can be blocklisted like any
+other type, i.e. <code>--blocklist-type &quot;__BindgenBitfieldUnit&quot;</code>. This may be useful if
+you want to define a custom implementation, or your generated bindings import a
+pre-existing definition for the bitfield unit type.</p>
 <h2><a class="header" href="#bitfield-examples" id="bitfield-examples">Bitfield examples</a></h2>
 <p>For this discussion, we will use the following C type definitions and functions.</p>
 <pre><code class="language-c">typedef struct {