2 ms·
Agreed, the guarantee that str only contains valid UTF-8 is nice and justifies a separate type, also the API hint ("this is expected to be an UTF-8 string, not
by flohofwoe 5y ago
Agreed, the guarantee that str only contains valid UTF-8 is nice and justifies a separate type, also the API hint ("this is expected to be an UTF-8 string, not a random bag of bytes") is a good thing. I don't know what the Zig team's stance is on builtin types vs stdlib wrapper types (assuming this can be expressed in a stdlib type, but I think it can), but either way it probably makes sense to introduce such a wrapper type relatively early (even if it's incomplete) to guide APIs towards using this.
Btw one thing that Zig has over Rust is that string literals are zero-terminated for C-compatibility (so the proper type is actually "[:0]const u8" - which is a "sentinel-terminated array"). This is in addition to strings being slices (pointers/size pairs), so despite being zero-terminated it doesn't inherit C's problems.
- tialaramex 5y agoPresumably the string literals are zero-terminated but other slices aren't? In a language that doesn't have safety promises that feels like a bug waiting to happen, somebody's code "works" with all the string literal test inputs but alas, real slices sometimes aren't followed by a zero terminator and it blows up nastily. And then also the same misfire can hurt in the other direction. Since Rust's str is really a UTF-8 slice, the zeroes are just zeroes, valid UTF-8 characters, you can ask if a Rust str contains(0 as char) because that's a completely reasonable question - but if your code thinks zero might be a "terminator" it can't actually handle arbitrary UTF-8 this way. Actually I think this makes the call for an actual str built-in even more appropriate because Zig's owners would need to wrestle with this and work out what they intended whereas just saying []const u8 allows you to hide inconsistencies in the libraries and people will get bitten.
- flohofwoe 5y agoSentinel-terminated arrays and slices have a different type than regular arrays and slices, and the sentinel isn't the terminator for the array or slice, just an additional item past the end. I think it's reasonably type-safe: https://ziglang.org/documentation/0.8.1/#Sentinel-Terminated-Arrays https://ziglang.org/documentation/0.8.1/#Sentinel-Terminated...