You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to golang-nuts
Please help me understand the type name format generated in debug info.
Mostly they seem to be in the <import-path>.<type-name> format, but sometimes _test is appended to import path. Also it seems like some parts of import path are url-encoded: type T defined in package pkg of the go module github.com/my/pkg.v2 gets name github.com/my/pkg%2ev2.T.
I wonder what are the rules for type names.
Thanks!
Ian Lance Taylor
unread,
Mar 4, 2021, 3:10:59 PM3/4/21
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Dmitry Neverov, golang-nuts
The _test appears in cases where the package name also ends in _test.
The %2e appears when the final element of an import path contains a
dot, to avoid getting it confused with the dot that separates the
package path from the name.