6151955420
We are working towards making exercises stand-alone. That is to say: no more generating READMEs on the fly. This will give maintainers more control over each individual exercise README, and it will also make some of the backend logic for delivering exercises simpler. The README template uses the Go text/template package, and the default templates generate the same READMEs as we have been generating on the fly. See the documentation in [regenerating exercise readmes][regenerate-docs] for details. The READMEs can be generated at any time using a new 'generate' command in configlet. This command has not yet landed in master or been released, but can be built from source in the generate-readmes branch on [configlet][]. [configlet]: https://github.com/exercism/configlet [regenerate-docs]: https://github.com/exercism/docs/blob/master/maintaining-a-track/regenerating-exercise-readmes.md |
||
|---|---|---|
| .. | ||
| tests | ||
| elm-package.json | ||
| Grains.elm | ||
| Grains.example.elm | ||
| package.json | ||
| README.md | ||
Grains
Calculate the number of grains of wheat on a chessboard given that the number on each square doubles.
There once was a wise servant who saved the life of a prince. The king promised to pay whatever the servant could dream up. Knowing that the king loved chess, the servant told the king he would like to have grains of wheat. One grain on the first square of a chess board. Two grains on the next. Four on the third, and so on.
There are 64 squares on a chessboard.
Write code that shows:
- how many grains were on each square, and
- the total number of grains
For bonus points
Did you get the tests passing and the code clean? If you want to, these are some additional things you could try:
- Optimize for speed.
- Optimize for readability.
Then please share your thoughts in a comment on the submission. Did this experiment make the code better? Worse? Did you learn anything from it?
Elm Installation
Refer to the Exercism help page for Elm installation and learning resources.
Writing the Code
The first time you start an exercise, you'll need to ensure you have the appropriate dependencies installed.
$ npm install
Execute the tests with:
$ npm test
Automatically run tests again when you save changes:
$ npm run watch
As you work your way through the test suite, be sure to remove the skip <|
calls from each test until you get them all passing!
Source
JavaRanch Cattle Drive, exercise 6 http://www.javaranch.com/grains.jsp
Submitting Incomplete Solutions
It's possible to submit an incomplete solution so you can see how others have completed the exercise.