Given that the go community does not seem to hold this as a majority opinion, you might consider whether an editor translation layer could allow you to tailor your environment to your preferences while maintaining source-level compatibility with the broader go community.
If compatibility is not as important to you, privately forking the language is also an option, but that seems fraught with peril of your code dying with you.
But the point is not my preference to use the actual, proper symbols, but rather the technically unnecessary decision forced upon me that says I cannot.
If compatibility is not as important to you, privately forking the language is also an option, but that seems fraught with peril of your code dying with you.