Re:Go’s runtime C to Go rewrite, by the numbers
by mholt on Monday September 01, 2014 @01:07AM
(#8251610)
Cool visualization. What causes the spikes? Code merges?
[ Parent
| on HN ]
Re:Go’s runtime C to Go rewrite, by the numbers
by vanderZwan on Monday September 01, 2014 @04:28AM
(#8251981)
Wouldn't make sense for the few solitary spike though. Perhaps they are found regressions, causing them to go back to the original C code for a while? That would make sense in the context of merges too - there's always a few bugs that show up under closer scrutiny.