You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,8 @@ with important features on the horizon. [Feedback](https://github.com/Intergated
8
8
9
9
What makes bitfilled different from the language standard's [bit fields][stdbitfield]?
10
10
11
-
1.**Portability** - regardless of platform or toolchain, the code behavior is the same (**except MSVC**, as it refuses to implement `[[no_unique_address]]`)
11
+
1.**Portability** - regardless of platform or toolchain, the code behavior is the same
12
+
(**except MSVC**, as it refuses to implement `[[no_unique_address]]`, so instead a compatible alternative is implemented with `__declspec(property())`)
12
13
2.**Performance** - optimized binary is identical to standard bit fields
13
14
3.**Flexibility** - allows bit fields on custom types, bit field arrays, and customizing bit operations (e.g. bit-banding)
14
15
@@ -83,12 +84,12 @@ Some examples are due:
83
84
(Do not be alarmed by the macros, their main purpose is to reduce the character count,
84
85
as having `[[no_unique_address]]` and a long type name isn't all that informative in this context.)
85
86
```cpp
86
-
#include <bitfilled/bitfilled.hpp>
87
+
#include <bitfilled.hpp>
87
88
struct myint : bitfilled::host_integer<unsigned>
88
89
{
89
90
BF_BITS(bool, 0) boolean; // 1 bit at offset 0
90
91
BF_BITS(std::memory_order, 1, 3) enumerated; // 3 bits at offset 1
0 commit comments