> String methods cover case conversion, trimming, searching, splitting, replacing, padding, classification, and parsing. .len() counts Unicode codepoints, not bytes; use .bytes().len() for raw byte length. Indexing with s[i] works in bytes; negative indices count from the end and out-of-bounds returns null. Several methods have aliases: .find() / .index_of(), .ltrim() / .trim_start(), etc.

Indexing uses bytes and len uses codepoints? Are you mad?

weirdUnicode[weirdUnicode.len()-1] returns random char?

And a = "a"; a[1] is null??

What does it do differently? What problem it solves that other languages don't?

Also, performance numbers. This looks highly complex and I worry that your C backend would underperform similar code in other languages. So let's us know.

In any case, on that one time that AI works perfectly, it saves me hours of coding. So the potential is there...

Personally, I don't like it much. It sounds like leakage from AzDO design. Maybe a option to turn it off would be the best way out.

Disclaimer: I work for msft, although I've no connection to github, ado or any other such tool.