doc: make it more explicit where print and println can be used #48029
Labels
Documentation
Issues describing a change to documentation.
NeedsDecision
Feedback is required from experts, contributors, and/or the community before a change can be made.
Milestone
Specification's "Bootstrapping" section mentions print and println can be removed from the language anytime, https://golang.org/ref/spec#Bootstrapping. But the section doesn't explain that they can be used in rare situations where importing fmt is not possible and it's otherwise better not to rely on them.
The community is confused due to existing reference code, examples and autogenerated code (by products like GitHub's Copilot) using print and println statements. The current wording in the section doesn't appear to be strong enough to discourage them and it might be useful to give more concrete reasons where the built in functions are suited to help them make the correct judgement.
The text was updated successfully, but these errors were encountered: