You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is obviously a big language design choice, but as I see it, we should either
make String a cover (would make for easier memory management, but probably break rock completely, and we would be back in Text territory...)
or
leave it as a class but modify the methods on String to allow editing an existing String instance instead of creating a new one (easy, since the underlying CharBuffer already does this!). This also simplifies a lot of the memory management code around strings we have today.
(Indeed, this is a big question requiring discussion, and maybe one that will never be fixed.)
The text was updated successfully, but these errors were encountered:
This is obviously a big language design choice, but as I see it, we should either
String
a cover (would make for easier memory management, but probably break rock completely, and we would be back inText
territory...)or
String
to allow editing an existingString
instance instead of creating a new one (easy, since the underlyingCharBuffer
already does this!). This also simplifies a lot of the memory management code around strings we have today.(Indeed, this is a big question requiring discussion, and maybe one that will never be fixed.)
The text was updated successfully, but these errors were encountered: