> Thanks! In addition to that, It also helps with code with upper limit > memory-requirement, which fmt.Sprintf() can't.
If you're processing data from untrusted sources, then you probably ought to validate it first. > How to use a limiting > io.Writer with fmt.Sprintf()? How would this limit fmt.Sprintf()'s > memory usage? Proof-of-concept: https://go.dev/play/p/kJabvvTzFH0 I don't know under what circumstances this would cause Fprintf to terminate early; it depends on how much buffering it does internally. I would guess that a large single argument like "%s" would be treated as a single entity, and very likely allocate an intermediate buffer of the full size. If this matters in your use case, then I think you shouldn't be using Sprintf and friends. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/960530e8-b872-4c86-8232-8fad8bd9d76cn%40googlegroups.com.
