Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Do you anticipate any reason we wouldn't ultimately be able to delete SBC? It is hard to think of a place we use it today that could not be refactored away one way or another.

Do you anticipate any reason we wouldn't ultimately be able to delete SBC? It is hard to think of a place we use it today that could not be refactored away one way or another.

There are always alternatives, and it's just a question of whether those alternatives are better for a given use. The primary benefit StringBuilder / StringBuilderCache can have in some situations is that it's segmented, such that other than for the final resulting string, you don't necessarily incur very large allocations, instead potentially incurring more, smaller allocations. It's just something to think about on a case-by-case basis, e.g. we'll need to think more about it for one of the two remaining uses in corelib, BinaryReader.ReadString.

Tagging subscribers to this area: @dotnet/area-system-runtime
See info in area-owners.md if you want to be subscribed.