Biases:
Process:
Download and run go/scanner.Scan
on all available versions
took approx 12h on Intel(R) Xeon(R) CPU E3-1240L v5 @ 2.10GHz
(4 core / 8 hyperthread) with 16GB ram (max ~10GB used).
Ever wondered how those versions are distributed?
by versions
What kind of parsing errors are there?
require(
note the missing space>>>>>>
, ======
, <<<<<<
)When do people pull in new code through the proxy?
What domains do modules live under?
do people use vanity domains or .$vcs
extension for their repos?
the following stats only count the latest version of every module
apparently documentation isn't good enough and people try to use invalid versions
who requires so many things?
todo: split by direct / indirect
todo: split by replace type
the exclude directive feels excluded
Since go.mod
doesn't include all imports
and I neglected to record the imports per package / file
I don't think I can do tokens - imports graph
(and find the left-pad equivalent in go)
10000 tokens is not too much, not too little
(the labels should be between the previous label and x)
ever wondered which operator was the most popular?
how many different identifiers do you need? a-z 26?
err??????
i have some doubts about this since who uses TRUE
, FALSE
,iNdEx
, dAtA
, autorest
ans: iNdEx
and dAtA
are from generated code, specifically from github.com/gogo/protobuf