Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Go encapsulation counts every lowercase symbol: 72% of a Go DOOM port lands in the encapsulation archetypes (C original 2%)

Aperta
  • Qualcosa non va?
#5,897 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go, python, rust
Ambito
tooling

Direzione di ricerca

Start with the Go encapsulation patterns in go.py and find their tests and goldens; use the supplied package main fixture to check that lowercase declarations produce no hits, then compare with a library-package case. Re-measure gore and inspect the Rust rule against the visibility question. Done means the acceptance checks pass, the archetype share is reported, and the rosetta expectations and goldens are updated with the drift explained.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

scope:frontier

Finding (DOOM study calibration, #5620)

Go's encapsulation rule counts every lowercase top-level symbol (go.py: ^func\s+(?:\([^)]*\)\s+)?[a-z]… and ^(type|var|const)\s+[a-z]…). keyword-rosetta ledgers this as intended visibility morphology (visibility-morphology-encapsulation, engine-semantic, validated 2026-08-31) and warns that "cross-language encapsulation comparisons must expect these to run structurally hot". On real translated code the effect is no longer a footnote. It decides the function archetypes the engine reports for Go.

Measurements at engine 9f213ab83, licensed DOOM ports, functions of at least 3 lines:

port language functions with an encapsulation hit hits / 100 LOC in the two encapsulation archetypes¹ Compute Cores
linuxdoom (original) C 5% 0.21 1.9% 34.3%
doom-scheme (translation) Scheme n/a n/a 1.5% 34.2%
gore (translation) Go 94% 3.09 71.8% 4.3%
dartdoom (translation) Dart 37% 1.54 31.3% 20.3%

¹ Encapsulated Accessors + Stateful Encapsulated Methods (k=14 function model).

gore keeps linuxdoom's call wiring (77% of linuxdoom's calls survive between the corresponding functions; structural-fingerprint-scanner subway maps, population-analyses examples/doom/), so the algorithm is the same. Yet nearly three quarters of its functions, renderer and playsim included, are labelled as encapsulation archetypes. Seven of gore's nine package clauses are package main, and 950 of its 1,025 func declarations are lowercase. In a main package nothing can be imported, so a lowercase name is not a visibility decision at all. The keyword-rosetta control shows the same skew on the identical planted program: def_encapsulation C 0, Java 0, Dart 0, C++ 0, Go 3.75, Rust 3.

Fixture (our own code, not from any port):

package main

func renderColumn(x int) int { // lowercase: counted as encapsulation today
	return x * 2
}

func main() {
	renderColumn(3)
}

Options

  1. Rule: in a package main file, lowercase declarations carry no visibility meaning, so don't count them. Optionally count only unexported methods and types in library packages. This is the smallest semantic fix.
  2. Model: keep the rule, but have the function-archetype classifier down-weight def_encapsulation for languages ledgered under visibility morphology (go, perl, and rust if confirmed), so the archetype labels stop tracking spelling.
  3. Leave it: document in the archetype docs that Go archetype mixes are not comparable with other languages.

Recommendation: option 1, which stays faithful to the ledger's "correct morphology" (library packages still count), then re-measure. If Go archetype mixes still diverge on translations that keep the original's wiring, do option 2 as well. Check Rust's rule against the same question (rosetta 3 vs 0).

Acceptance

  • The fixture above: 0 encapsulation hits in package main; a library-package variant still counts its unexported functions (test).
  • gore's encapsulation-archetype share re-measured and posted here (target: within ~10 points of the C original's, or the residual explained).
  • keyword-rosetta visibility-morphology-encapsulation updated (Go expected counts re-locked), and goldens re-blessed with the drift explained.

Part of #5457; calibration finding for #5620. Data: structural-fingerprint-scanner per-subsystem view (gitgalaxy-population-analyses PR #19).

Lingua principale
Python
Stelle
57
Fork
11
Merge medio
1h 32m
PR unite (30g)
990

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di squid-protocol/gitgalaxy

Tutte le issue di squid-protocol/gitgalaxy

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.