Skip to content

work on char/str descriptions #809

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
May 14, 2020
Merged

work on char/str descriptions #809

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
dcf0963
work on char/str descriptions
RalfJung May 12, 2020
3c6a8f4
fix link
RalfJung May 12, 2020
bd74860
clarify representation
RalfJung May 12, 2020
ed7ad72
tweak str wording
RalfJung May 13, 2020
9af5071
Split str DST into a separate paragraph.
ehuss May 14, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
clarify representation
  • Loading branch information
@RalfJung
RalfJung committed May 12, 2020
commit bd74860ea129c954b16d751d957be43c6795c6ee
12 changes: 6 additions & 6 deletions src/types/textual.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,12 +9,12 @@ or 0xE000 to 0x10FFFF range. It is immediate [Undefined Behavior] to create a
string of length 1.

A value of type `str` is a Unicode string, represented as an array of 8-bit
unsigned bytes holding a sequence of UTF-8 code points. Note that this is a
library-level invariant: for the compiler and core language specification, `str`
is the same as `[u8]`, but methods working on `str` may assume that the data in
there is valid UTF-8 and may cause Undefined Behavior otherwise. Since `str` is
a [dynamically sized type], it can only be instantiated through a pointer type,
such as `&str`.
unsigned bytes holding a sequence of UTF-8 encoded Unicode code points. Note
that this is a library-level invariant: for the compiler and core language
specification, `str` is the same as `[u8]`, but methods working on `str` may
assume that the data in there is valid UTF-8 and may cause Undefined Behavior
otherwise. Since `str` is a [dynamically sized type], it can only be
instantiated through a pointer type, such as `&str`.

[Unicode scalar value]: http://www.unicode.org/glossary/#unicode_scalar_value
[Undefined Behavior]: ../behavior-considered-undefined.md
Expand Down