Skip to content

Commit 01e9ad9

Browse files
committed
Additional clarification of current state of affairs
1 parent 643f769 commit 01e9ad9

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

active/0000-unsafe-api-location.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -26,9 +26,10 @@ provides:
2626
of the string, but thereby also allows violation of the utf8 guarantee.
2727

2828
* A `raw` submodule with a number of free functions, like `from_parts`, that
29-
construct `String` instances from various raw-pointer-based representations,
30-
as well as a `from_utf8` variant that does not actually check for utf8
31-
validity.
29+
constructs a `String` instances from a raw-pointer-based representation, a
30+
`from_utf8` variant that does not actually check for utf8 validity, and so
31+
on. The unifying theme is that all of these functions avoid checking some key
32+
invariant.
3233

3334
The problem is that currently, there is no clear/consistent guideline about
3435
which of these APIs should live as methods/static functions associated with a

0 commit comments

Comments
 (0)