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
All functions construct their own StringBuilder instance, it would be great if users can pass an existing one, in case they use these functions as part of building another, bigger string.
Obviously it would be best if it would be possible to integrate seamlessly with functions like buildString in a way that users do not even have to pass in anything. However, this is impossible until we have multiple receiver support in Kotlin. But, we can add extension functions to StringBuilder instead that are almost as awesome. 😎
All functions construct their own
StringBuilder
instance, it would be great if users can pass an existing one, in case they use these functions as part of building another, bigger string.Obviously it would be best if it would be possible to integrate seamlessly with functions like
buildString
in a way that users do not even have to pass in anything. However, this is impossible until we have multiple receiver support in Kotlin. But, we can add extension functions toStringBuilder
instead that are almost as awesome. 😎The text was updated successfully, but these errors were encountered: