Timeline for Count the length of head movement
Current License: CC BY-SA 4.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Dec 14, 2019 at 0:01 | history | tweeted | twitter.com/StackCodeGolf/status/1205638785523957762 | ||
Dec 13, 2019 at 17:33 | history | reopened |
Jo King♦ Stephen Wheat Wizard♦ fəˈnɛtɪk Mr. Xcoder |
||
Dec 13, 2019 at 8:40 | review | Reopen votes | |||
Dec 13, 2019 at 17:33 | |||||
Dec 13, 2019 at 8:21 | history | edited | CuttingChipset | CC BY-SA 4.0 |
Clarifying the rules uncaught in sandbox
|
Dec 10, 2019 at 11:39 | history | closed |
Grimmy caird coinheringaahin g♦ Riker Gymhgy the default. |
Needs details or clarity | |
Dec 9, 2019 at 17:15 | review | Close votes | |||
Dec 10, 2019 at 11:39 | |||||
Dec 9, 2019 at 17:00 | comment | added | Grimmy | The output is defined as the distance that the head moves, but there's almost no explanation of how the head moves. Each character is associated with a "value"; are those actually distances? "The head moves from the end of the first cut to the beginning of the second cut in a straight line"; is that specific to the first cut, or true for all pairs of consecutive cuts? | |
Dec 9, 2019 at 15:43 | comment | added | Grimmy |
You should explain what you mean by "next to a diagonal cut". I thought it'd mean adjacent to # or @ (since 45° and 135° lines are diagonals), but this doesn't fit with the test cases.
|
|
Dec 9, 2019 at 13:13 | comment | added | Veskah | Can we use swap the 4 90 degree cut symbols for ASCII symbols (e.g. use 1,2,3,4) instead? | |
Dec 9, 2019 at 11:20 | history | asked | CuttingChipset | CC BY-SA 4.0 |