Ldont mix
A
Mwatch me
Lyes and?
Lutf-8 supports all unicode values? thats its whole point
Anono as in
Ldo you mean "strict ascii"?
Ait converts it to 1 byte per character
Ayes
Tyou're not meant to index strings 
L^
Aand then whatever the fuck the last 127 numbers of ascii are called
Awhich is apparently not utf-8 because why would be it
Mtheyre called nothing
Mbecause they dont exist
Lyou shouldnt index strings since that doesnt really makes sense and could mean 8 million things
PASCII is 7-bit
Literate over codepoints or unicode scalar values
MASCII is 7-bit clean, it doesn't specify what goes in the other bit, or if one exists
Pwhich is probably why it was so easy to model UTF-8 on a napkin
Pwhich is actually how it was invented
Mbetter than the best thing i've done on a napkin
Tapparently "str".chars().nth(1) works 
Aall i wanna do is go
why is this so hard
if string[1] == 'c' likewhy is this so hard
Ait does yes
Abut that also iterates through the entire damn string
Lbecause langauge is hard
Aevery time you call it
Lits just not that simple
Mof course it was a sad day for everyone using the "extended ASCII" encodings
Mor non-ASCII
Tsimple, just don't 
Adfjkghlsjdfg
Mstep 1. delete rust
step 2. use c#
step 2. use c#
Pwow that codegen is laughable https://godbolt.org/z/zv9McWTEK
Astep 3. delete c#
step 4. return to c
step 4. return to c
Pthat's with maximum optimisation
Mwhat the fuck
Ayep
Mthis shit is in firefox?? 
Ay e p
Athe best way to do this is genuinely to allocate an entirely new damn array
Pmarginally better https://godbolt.org/z/87vjddjY3
Lnow get the 2nd char in a C string
Awhich just is major pain
PMajor Pain 
Mdo what all c++ programmers do and roll your own string type
Asimple,
and if you have a japanese character then just
just
give up
perfect!!!
thing[1]and if you have a japanese character then just
just
give up
perfect!!!
Mthere are algorithms for this
Lcorrect