Earlier quoted context omitted.
Based on the commit message and using "CL" which is google lingo for Change List on their internal system, I bet this was already available on the internal version and just ported to github version after someone pointed it out.
"CL"/"Change List" is the lingo for the Gerrit code review tool, which is how all contributions to Go happen. Creating a GitHub PR simply triggers a bot to create a Gerrit CL, which is where all discussion about the "PR" happens and where the "accept" button gets clicked.
Losing 1½ Million Lines of Go
11–14 of 14 posts
Re: Losing 1½ Million Lines of Go
#12Earlier quoted context omitted.
"CL"/"Change List" is the lingo for the Gerrit code review tool, which is how all contributions to Go happen. Creating a GitHub PR simply triggers a bot to create a Gerrit CL, which is where all discussion about the "PR" happens and where the "accept" button gets clicked.
Is Gerrit the same as Critique?
Re: Losing 1½ Million Lines of Go
#13> Sure, these automata are “wide”, with lots of branches, but they’re also shallow, since they run on UTF-8 encoded characters whose maximum length is four and average length is much less I would consider splitting this task into two: - extracting the next Unicode code unit - determining whether it’s in the code class For the second, instead of using an automaton, one could use a perfect hash ( https://en.wikipedia.o…