Rosetta Code:Add a Task: Difference between revisions
Content added Content deleted
(→Task focus exclusion: Emphasize sections, to reduce wall-of-text.) |
(→Basic information: Solidify language, use emphasis on key points to reduce wall-of-text.) |
||
| Line 33: | Line 33: | ||
===Basic information=== |
===Basic information=== |
||
A task needs a few basic components. It neeeds a '''simple description of the problem'''. Having a solution to the task allows you to tune the task description such that the run times and/or size of outputs are reasonable. |
|||
* Inline references to specifically-related information.<br>Although links to offsite information do help in a task description, it is best to have enough of a description of the task on the R.C. site itself. |
|||
'''Inline references to specifically-related information''' are important. While offsite links are often necessary (if only for appropriate citation), enough cited, excerpted information should be included such that the task may still be solved. |
|||
* Sample input (where relevant; it depends on the task) |
|||
Where relevant, '''sample input''' should be included; it gives task solvers something to work with. |
|||
===Example code=== |
===Example code=== |
||