Re:Go’s runtime C to Go rewrite, by the numbers
by seanmcdirmid on Monday September 01, 2014 @03:26AM
(#8251844)
That is easy to check, could the author put 100 lines of C code next to 100 lines of equivalent Go code and let us judge for ourselves?
[ Parent
| on HN ]
Re:Go’s runtime C to Go rewrite, by the numbers
by sambeau on Monday September 01, 2014 @06:02AM
(#8252181)
If we judge for ourselves we will only be checking our opinion.
Could you provide a readability algorithm in some form of executable that we can run against the 100 lines of c and Go code — then we'll be able to judge correctly.
Re:Go’s runtime C to Go rewrite, by the numbers
by pjc50 on Monday September 01, 2014 @08:34AM
(#8252523)
readability algorithm
Sure, it's next to the objective poetry quality metric.
"Shall I compare thee to a summer's day?"
> TYPE ERROR
Re:Go’s runtime C to Go rewrite, by the numbers
by seanmcdirmid on Monday September 01, 2014 @06:14AM
(#8252211)
Honestly, I just want to see them side by side. We can then debate our subjective interpretations vs. debating pure biases.
Re:Go’s runtime C to Go rewrite, by the numbers
by 4ad on Monday September 01, 2014 @06:26AM
(#8252244)
A random list of CLs that dealt with conversions.
https://codereview.appspot.com/99380043
https://codereview.appspot.com/140050044
https://codereview.appspot.com/136980044
https://codereview.appspot.com/139930044
https://codereview.appspot.com/139930043
https://codereview.appspot.com/135070043
https://codereview.appspot.com/123700044
https://codereview.appspot.com/126210046
https://codereview.appspot.com/130340043