golang/go

cmd/compile: review compiler-generated symbol naming scheme

Open

#35,088 opened on Oct 22, 2019

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (19,008 forks)batch import
NeedsInvestigationcompiler/runtimehelp wanted

Repository metrics

Stars
 (133,883 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

cmd/compile generates a lot of linker symbols for internal objects, and we've amassed a number of ad hoc naming schemes for them. I'm concerned that there might be collisions, particularly with user-defined symbols.

We should review and probably catalog the existing symbol, and try to find a more uniform naming scheme that we can ensure is collision-free.

Contributor guide

Research direction
Review the existing symbol naming schemes in cmd/compile and propose a uniform, collision free naming convention.
Tech stack
go
Domain
backend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20