Lines Matching refs:it

22 `strncmp` is always wrong with -fbounds-safety, and it's unavailable as a
31 Using `strncmp` with two NUL-terminated strings is uncommon and it has no
85 cases, it can also lead to stability issues.
92 instance. However, it creates new problems:
103 * `tsnprintf`: like `snprintf`, but it returns a NUL-terminated string;
127 of indexable pointer, and only once you're done should you convert it to a
147 while it's still being modified. Keeping my_string a `__null_terminated` pointer
148 while it's being modified leads to more forging, which has more chances of
163 it ergonomically, and importantly, without forging. You turn it into a
164 NUL-terminated string at the same time you turn it into a `const` reference,
168 a character array such that you get a NUL-terminated view of it. For instance,
201 When possible, it's advised to use APIs that copy NUL-terminated pointers (like
205 (if you need it). Also keep in mind that in code which pervasively deals with
207 strings, it could be simply more convenient to keep string buffers in some
231 Without -fbounds-safety, these all work the same, but when you enable it,