How do you handle whether a symbol identifier is public or private?

On 2025-10-01 11:31, robert engels wrote:
I agree - if you already allow non-ascii symbols - what’s the difference. It’s up to the owner of the code base to decide if it works better for them or not.

On Oct 1, 2025, at 10:24 AM, awaw...@gmail.com <awawfu...@gmail.com> wrote:

Thanks for chiming in.

I wonder could you or others elaborate on why allowing math symbols would make it harder than present to search for? At present, in Go we can already do Japanese hiragana and katagana, not to mention emojis, whose search requirements are no different than Math symbols. In fact, I use the ancient Vim editor (without any plugins) as I'm old fashioned, and Vim doesn't seem to have issues searching for "⊗".
I suppose the search experience is even better in VSCode or github.

Regarding the concern that:
> symbols may be meaningful to the author, code consumers find it harder.
At present, Go supports ℏ(reduced Planck constant) and *Δ*p (momentum deviation), which arguably is meaningful not only to authors but also code consumers. ⊗ may seem foreign to most Physics undergraduates, but its meaning is no doubt *universal* among quantum technology practitioners. I appreciate if anyone could provide an example or scenario on code consumers of a quantum related Go package finding it hard to read σXas the Pauli X matrix or ⊗ as the tensor product. In other words, within a specific domain, judiciously chosen special symbols actually help code readability.

Sorry if I may sound a bit absurd or combative (I'm sincerely not), but I am just believing that laying out concrete details and examples helps make decisions whether pro or con.

On Wednesday, October 1, 2025 at 3:53:54 PM UTC+8 Dan Kortschak wrote:

    On Wed, 2025-10-01 at 00:42 -0700, awaw...@gmail.com wrote:
    > func ⊗(ops *tensor.Dense) *tensor.Dense {...}

    Please no. Including these make the code much harder to work in
    as it
    is harder to search for and while the symbols may be meaningful
    to the
    author, code consumers find it harder. If you need maths symbols,
    put
    them in the godoc.


--
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 visit https://groups.google.com/d/msgid/golang-nuts/39e212d7-a5d1-438f-8116-8e929b835da4n%40googlegroups.com <https://groups.google.com/d/msgid/golang-nuts/39e212d7-a5d1-438f-8116-8e929b835da4n%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
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 visit https://groups.google.com/d/msgid/golang-nuts/EE71219E-FF34-42BB-BAFF-1D516EDC7DF8%40ix.netcom.com <https://groups.google.com/d/msgid/golang-nuts/EE71219E-FF34-42BB-BAFF-1D516EDC7DF8%40ix.netcom.com?utm_medium=email&utm_source=footer>.

--
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 visit 
https://groups.google.com/d/msgid/golang-nuts/7f185c31-b69e-460f-92c8-65cfab845d39%40gmail.com.

Reply via email to