Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change.

Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change.

I am wondering if concerns about exposing ValueStringBuilder are not applicable here too. Soon I've copied ValueStingBuilder in our codebase and build a handler like DefaultInterpolatedStringHandler but storage was VSB. Then was asked by colleagues what will happen if they forgot about calling Clear(Dispose in our case).

Then was asked by colleagues what will happen if they forgot about calling Clear(Dispose in our case).

An ArrayPool array may not be returned to the pool.

Is there any particular reason why Text and ToString aren't marked readonly, btw?

@hamarb123 valid question; they probably could/should be

Is there any particular reason why Text and ToString aren't marked readonly, btw?

@hamarb123 valid question; they probably could/should be

Lots of members could be. Why should these be? Passing around a DefaultInterpolatedStringHandler by in seems like a bad idea.

You're right, upon consideration; adding readonly is only useful on a flavor of usage that actively does not apply to this type.

@mgravell @stephentoub - should we announce this one in dotnet/core#9824?

@ericstj possibly too niche - maybe better to wait until I get the related HybridCache changes merged (which are more consumer-facing), and announce all together as a related batch?

Sure, just pinging on the PRs that look like they might be interesting.