The current string is always a string view usually into the source code itself (for string literals). This is simple and quite nice for constant strings that do not change. However it's quite tedious to create new strings (that are not simple views into the source). Another possible "downside" is that the string is immutable. This is not inherently bad and maybe the preferred property in many cases. That said - I'd like to delve into the possibility of having a dynamic string type. I think string operations will be very common, and so I have an inclination that a dynamic string type may be better. This would mean the string would have to live on the malloc heap and not the "stack" (scope arena).
LytixDev
commented
1 year ago
The current string is always a string view usually into the source code itself (for string literals). This is simple and quite nice for constant strings that do not change. However it's quite tedious to create new strings (that are not simple views into the source). Another possible "downside" is that the string is immutable. This is not inherently bad and maybe the preferred property in many cases. That said - I'd like to delve into the possibility of having a dynamic string type. I think string operations will be very common, and so I have an inclination that a dynamic string type may be better. This would mean the string would have to live on the malloc heap and not the "stack" (scope arena).