Brian Buller
739f3c3e2b
|
||
|---|---|---|
| .. | ||
| README.md | ||
| hello_test.d | ||
| hello_world.d | ||
README.md
Hello World
Write a function that greets the user by name, or by saying "Hello, World!" if no name is given.
"Hello, World!" is the traditional first program for beginning programming in a new language.
Note: You can skip this exercise by running:
exercism skip $LANGUAGE hello-world
Specification
Write a Hello World! function that can greet someone given their name.
The function should return the appropriate greeting.
For an input of "Alice", the response should be "Hello, Alice!".
If a name is not given, the response should be "Hello, World!"
Test-Driven Development
As programmers mature, they eventually want to test their code.
Here at Exercism we simulate Test-Driven Development (TDD), where you write your tests before writing any functionality. The simulation comes in the form of a pre-written test suite, which will signal that you have solved the problem.
It will also provide you with a safety net to explore other solutions without breaking the functionality.
A typical TDD workflow on Exercism:
- Run the test file and pick one test that's failing.
- Write some code to fix the test you picked.
- Re-run the tests to confirm the test is now passing.
- Repeat from step 1.
- Submit your solution (
exercism submit /path/to/file)
Instructions
Submissions are encouraged to be general, within reason. Having said that, it's also important not to over-engineer a solution.
It's important to remember that the goal is to make code as expressive and readable as we can. However, solutions to the hello-world exercise will not be reviewed by a person, but by rikki- the robot, who will offer an encouraging word.
Getting Started
Make sure you have read D page on exercism.io. This covers the basic information on setting up the development environment expected by the exercises.
Passing the Tests
Get the first test compiling, linking and passing by following the three rules of test-driven development. Create just enough structure by declaring namespaces, functions, classes, etc., to satisfy any compiler errors and get the test to fail. Then write just enough code to get the test to pass. Once you've done that, uncomment the next test by moving the following line past the next test.
static if (all_tests_enabled)
This may result in compile errors as new constructs may be invoked that you haven't yet declared or defined. Again, fix the compile errors minimally to get a failing test, then change the code minimally to pass the test, refactor your implementation for readability and expressiveness and then go on to the next test.
Try to use standard D facilities in preference to writing your own low-level algorithms or facilities by hand. DRefLanguage and DReference are references to the D language and D standard library.
Source
This is an exercise to introduce users to using Exercism http://en.wikipedia.org/wiki/%22Hello,_world!%22_program
Submitting Incomplete Problems
It's possible to submit an incomplete solution so you can see how others have completed the exercise.