Skip to content

Commit 5a8d2a6

Browse files
JPBetleyIanWhitney
authored andcommitted
Explicitly describe robot name format (#283)
The definition of this problem led to some confusion in the scala test case. Some languages expect differing formats for the robots names. This is an attempt to make it explicit and clear to the end-users and the problem creators to avoid this ambiguity. An example of this issue can be found in this PR: exercism/scala#123 If this PR is accepted, I will be more than happy to check the languages that have the "Robot Name" problem to make sure each language's tests are consistent.
1 parent c4c5f25 commit 5a8d2a6

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

robot-name.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
When robots come off the factory floor, they have no name.
22

3-
The first time you boot them up, a random name is generated, such as
4-
RX837 or BC811.
3+
The first time you boot them up, a random name is generated in the format
4+
of two uppercase letters followed by three digits, such as RX837 or BC811.
55

66
Every once in a while we need to reset a robot to its factory settings,
77
which means that their name gets wiped. The next time you ask, it will

0 commit comments

Comments
 (0)