|Subject:||[RFC] native 'str' type unspecced, undocumented, and ill-defined|
We've had a native 'str' type for a while, and still have one even though NativeCall decided to go with Str and 'is encoded'. Currently it seems to just be a Str under the hood which has very few restrictions, other than not allowing binding to a Str. What exactly is a 'str'? Is it null terminated or does it know its length? Does it have an encoding? Roast indicates it knows how to take an assignment from a Str literal (but no literal is used that pushes any boundaries) and can be used in multi-dispatch and... that's really about all.