Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 6
    \$\begingroup\$ Considering that the other question is a fastest-code code-challenge without an objective winning criterion (fastest measured how?), I propose closing the other and reopening this one. \$\endgroup\$ Commented Jul 3, 2014 at 12:59
  • 2
    \$\begingroup\$ I agree with @dennis and therefore I have upvoted the following unpopular answer on the original question. "If the answer you are looking for is strictly a fast result, then if you declare an array (of the gray codes)..." However the original question aready has a 7-character and a 4-character answer so I don´t see much room for improvement. Therefore I am not casting a reopen vote at present. \$\endgroup\$ Commented Jul 3, 2014 at 13:10
  • 3
    \$\begingroup\$ It's awfully similar to Traverse all numbers with only one bit flip per step though... \$\endgroup\$ Commented Jul 3, 2014 at 13:58
  • \$\begingroup\$ The earliest Gray code question isn't great, but it already has answers which are fundamentally the same as the answers which this question wants, and which are not likely to be improved. I think it would have made more sense to leave this one closed and change the other one to a code golf. \$\endgroup\$ Commented Jul 3, 2014 at 15:57