| MEDIUM | test/codegen/comparisons.go | 309 | // CMN and CMP for subtraction expressions to make the pattern robust. | COMMENT |
| LOW | src/make.bash | 61 | # (Or just pass them to the make.bash command line.) | COMMENT |
| MEDIUM | src/cmd/go/alldocs.go | 2298 | // Consumers should be robust to this. | COMMENT |
| MEDIUM | src/cmd/go/internal/work/exec.go | 3027 | // Definitely want -fPIC but on Windows gcc complains | COMMENT |
| MEDIUM | src/cmd/trace/pprof.go | 243 | // Because slices aren't comparable and we want to leverage maps for deduplication, | COMMENT |
| MEDIUM | src/cmd/internal/obj/dwarf.go | 98 | // https://github.com/go-delve/delve/issues/1694), however the bug | COMMENT |
| LOW | src/cmd/internal/test2json/testdata/benchshort.json | 5 | {"Action":"output","Output":"# but to avoid questions of timing, we just use a file with no \\n at all.\n"} | CODE |
| MEDIUM | src/cmd/internal/src/pos.go | 391 | // Depending on the debugger (gdb or delve) it may or may not be displayed. | COMMENT |
| MEDIUM | src/cmd/internal/src/xpos.go | 73 | // gdb chooses not to display the bogus line; delve shows it with a complaint, but the | COMMENT |
| MEDIUM | src/cmd/compile/internal/noder/reader.go | 2734 | // TODO(mdempsky): Is there a more robust way to get the | COMMENT |
| MEDIUM | src/cmd/compile/internal/noder/reader.go | 3027 | // TODO(mdempsky): Is there a more robust way to get the | COMMENT |
| MEDIUM | src/cmd/compile/internal/noder/reader.go | 3126 | // TODO(mark): It's not ideal to rely on string naming here. Find a more robust solution. | COMMENT |
| MEDIUM | src/cmd/compile/internal/noder/reader.go | 4372 | // https://github.com/go-delve/delve/blob/cb91509630529e6055be845688fd21eb89ae8714/pkg/proc/eval.go#L28 | COMMENT |
| MEDIUM | src/cmd/compile/internal/types2/context_test.go | 21 | // make them robust to internal type assertions, but could equally well use | COMMENT |
| MEDIUM | src/cmd/compile/internal/types2/context.go | 31 | // Nevertheless, in the future it could be helpful to allow users to leverage | COMMENT |
| MEDIUM | src/cmd/compile/internal/ssa/debug.go | 98 | // #yield is used by delve. | COMMENT |
| MEDIUM | src/cmd/compile/internal/ssa/debug.go | 98 | // #yield is used by delve. | COMMENT |
| MEDIUM | src/cmd/compile/internal/ssa/known_bits.go | 374 | // We also leverage known bits of the shift amount to remove "branches" in the switch that are proved to be impossible. | COMMENT |
| MEDIUM | src/cmd/compile/internal/ssa/dom.go | 8 | // This seems to make loop-finding more robust. | COMMENT |
| MEDIUM | src/cmd/compile/internal/ssa/debug_test.go | 50 | // TestNexting go-builds a file, then uses a debugger (default delve, optionally gdb) | COMMENT |
| MEDIUM | src/cmd/compile/internal/ssa/testdata/scopes.go | 33 | for x := 0; x <= 1; x++ { // From delve scopetest.go | CODE |
| MEDIUM | src/cmd/compile/internal/ssa/testdata/scopes.go | 51 | { // From delve testnextprog.go | CODE |
| MEDIUM | src/cmd/cgo/out.go | 1102 | // string.h for memset, and is also robust to C++ | COMMENT |
| MEDIUM | src/cmd/cgo/gcc.go | 469 | // but usually it does. Certainly if we don't see the completed:1 error, we did | COMMENT |
| MEDIUM | src/cmd/covdata/tool_test.go | 29 | // TestMain used here so that we can leverage the test executable | COMMENT |
| MEDIUM | src/cmd/cover/cover_test.go | 48 | // TestMain used here so that we can leverage the test executable | COMMENT |
| MEDIUM | src/net/dnsclient_unix_test.go | 1478 | // Return NXDOMAIN to utilize the search list. | COMMENT |
| MEDIUM | src/net/http/serve_test.go | 1001 | // TODO(panjf2000): sleep is not so robust, maybe find a better way to test this? | COMMENT |
| MEDIUM | src/go/token/position.go | 548 | // The iterator is robust to modification by yield. | COMMENT |
| MEDIUM | src/go/types/context_test.go | 24 | // make them robust to internal type assertions, but could equally well use | COMMENT |
| MEDIUM | src/go/types/context.go | 34 | // Nevertheless, in the future it could be helpful to allow users to leverage | COMMENT |
| MEDIUM | src/go/printer/testdata/parser.go | 579 | // it here for more robust parsing and better error messages | COMMENT |
| MEDIUM | src/go/printer/testdata/parser.go | 637 | // accept them all for more robust parsing and complain | COMMENT |
| MEDIUM | src/go/internal/gcimporter/gcimporter_test.go | 174 | // the files we consider in an attempt to make this test more robust to | COMMENT |
| MEDIUM | src/go/parser/parser.go | 748 | // it here for more robust parsing and better error messages | COMMENT |
| MEDIUM | src/runtime/proc.go | 37 | // We need to balance between keeping enough running worker threads to utilize | COMMENT |
| MEDIUM | src/runtime/metrics.go | 1027 | // Broken out for more robust testing. metricsLock must be held and | COMMENT |
| MEDIUM | src/runtime/proc_test.go | 490 | // fairly large factor here to make this robust: if the | COMMENT |
| MEDIUM | src/runtime/mpagealloc_test.go | 623 | // Test to check for issue #40191. Essentially, the candidate searchAddr | COMMENT |
| MEDIUM | src/runtime/mpagealloc_test.go | 623 | // Test to check for issue #40191. Essentially, the candidate searchAddr | COMMENT |
| MEDIUM | src/runtime/mgcpacer_test.go | 404 | // Provide a lot of room for the limit. Essentially, this should behave just like | COMMENT |
| MEDIUM | src/runtime/export_test.go | 1719 | // a bit more robust. | COMMENT |
| MEDIUM | src/runtime/mpagealloc.go | 165 | // This is slightly more nuanced than just a shift for the exclusive | COMMENT |
| MEDIUM | src/runtime/symtabinl_test.go | 48 | // this robust. | COMMENT |
| MEDIUM | src/runtime/complex.go | 20 | // Algorithm for robust complex division as described in | COMMENT |
| MEDIUM | src/runtime/mprof.go | 965 | // Absolutely no data, suggesting that a garbage collection | COMMENT |
| MEDIUM | src/runtime/mgcscavenge.go | 28 | // Essentially, we wish to have the application's RSS track the heap goal, but | COMMENT |
| MEDIUM | src/runtime/pprof/label.go | 96 | // Currently only the CPU and goroutine profiles utilize any labels | COMMENT |
| MEDIUM | src/internal/trace/gc.go | 131 | // It will show up very early in the trace, but we need to be robust to | COMMENT |
| MEDIUM | src/internal/trace/event.go | 838 | // may be tracked in the future, and callers must be robust to this | COMMENT |
| MEDIUM | src/internal/trace/resources.go | 35 | // New GoStates may be added in the future. Users of this type must be robust | COMMENT |
| MEDIUM | src/internal/trace/resources.go | 77 | // New ProcStates may be added in the future. Users of this type must be robust | COMMENT |
| MEDIUM | src/internal/trace/resources.go | 113 | // New ResourceKinds may be added in the future. Users of this type must be robust | COMMENT |
| MEDIUM | src/internal/trace/value.go | 32 | // New ValueKinds may be added in the future. Users of this type must be robust | COMMENT |
| MEDIUM | src/internal/runtime/gc/scan/mkasm.go | 128 | // shuffle those bytes together. Certainly for f >= 16 this makes sense | COMMENT |
| MEDIUM | src/simd/archsimd/_gen/unify/closure.go | 119 | // Essentially the same as Def. | COMMENT |
| LOW | …d/archsimd/_gen/simdgen/ops/BitwiseLogic/go_amd64.yaml | 28 | # for unmasked operations, right now we don't realize that we can just use the | COMMENT |
| MEDIUM | src/time/time.go | 32 | // time.Now().Before(deadline), are similarly robust against wall clock | COMMENT |
| MEDIUM | src/testing/testing.go | 117 | // statistically robust A/B comparisons. | COMMENT |
| MEDIUM | src/testing/testing.go | 147 | // New benchmarks should prefer using [B.Loop], which is more robust | COMMENT |
| 1 more matches not shown… |
Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).