summaryrefslogtreecommitdiff
path: root/doc/macros.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/macros.md')
-rw-r--r--doc/macros.md31
1 files changed, 31 insertions, 0 deletions
diff --git a/doc/macros.md b/doc/macros.md
new file mode 100644
index 0000000..e18553b
--- /dev/null
+++ b/doc/macros.md
@@ -0,0 +1,31 @@
+# Constructor Macros
+
+This module provides macros that can be used to create `bitvec` data buffers at
+compile time. Each data structure has a corresponding macro:
+
+- `BitSlice` has [`bits!`]
+- `BitArray` has [`bitarr!`] (and [`BitArr!`] to produce type expressions)
+- `BitBox` has [`bitbox!`]
+- `BitVec` has [`bitvec!`]
+
+These macros take a sequence of bit literals, as well as some optional control
+prefixes, and expand to code that is generally solvable at compile-time. The
+provided bit-orderings `Lsb0` and `Msb0` have implementations that can be used
+in `const` contexts, while third-party user-provided orderings cannot be used in
+`const` contexts but almost certainly *can* be const-folded by LLVM.
+
+The sequences are encoded into element literals during compilation, and will be
+correctly encoded into the target binary. This is even true for targets with
+differing byte-endianness than the host compiler.
+
+See each macro for documentation on its invocation syntax. The general pattern
+is `[modifier] [T, O;] bits…`. The modifiers influence the nature of the
+produced binding, the `[T, O;]` pair provides type parameters when the default
+is undesirable, and the `bits…` provides the actual contents of the data
+buffer.
+
+[`BitArr!`]: macro@crate::BitArr
+[`bitarr!`]: macro@crate::bitarr
+[`bitbox!`]: macro@crate::bitbox
+[`bits!`]: macro@crate::bits
+[`bitvec!`]: macro@crate::bitvec