From a9ae4ebc6006271fc0e95626e0c95e6b9cc786de Mon Sep 17 00:00:00 2001 From: Dimitri Sokolyuk Date: Sun, 28 Aug 2016 14:41:56 +0200 Subject: Solve robot --- go/robot-name/README.md | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) create mode 100644 go/robot-name/README.md (limited to 'go/robot-name/README.md') diff --git a/go/robot-name/README.md b/go/robot-name/README.md new file mode 100644 index 0000000..5063b90 --- /dev/null +++ b/go/robot-name/README.md @@ -0,0 +1,35 @@ +# Robot Name + +Write a program that manages robot factory settings. + +When robots come off the factory floor, they have no name. + +The first time you boot them up, a random name is generated in the format +of two uppercase letters followed by three digits, such as RX837 or BC811. + +Every once in a while we need to reset a robot to its factory settings, +which means that their name gets wiped. The next time you ask, it will +respond with a new random name. + +The names must be random: they should not follow a predictable sequence. +Random names means a risk of collisions. Your solution should not allow +the use of the same name twice when avoidable. In some exercism language +tracks there are tests to ensure that the same name is never used twice. + +To run the tests simply run the command `go test` in the exercise directory. + +If the test suite contains benchmarks, you can run these with the `-bench` +flag: + + go test -bench . + +For more detailed info about the Go track see the [help +page](http://exercism.io/languages/go). + +## Source + +A debugging session with Paul Blackwell at gSchool. [http://gschool.it](http://gschool.it) + +## Submitting Incomplete Problems +It's possible to submit an incomplete solution so you can see how others have completed the exercise. + -- cgit v1.2.3