Anonymous user
User talk:Dchapes: Difference between revisions
→Go Sum digits task: subpages
(→Go Sum digits task: subpages) |
|||
Line 10:
::It's kind of sad that the way sites like RosettaCode are done make it hard to do the "right thing" for languages like Go (multiple files, with extra test code files and separate main "demo programs", proper revision control, etc). Among other things it doesn't let us show off one of the great aspects of Go (IMO) which is the testing and build infrastructure.
::Actually, on that note, does it makes any sense (and is there a reasonably nice way on RosettaCode) to provide extra non-example test files? Something that doesn't show up directly on the example page (it would be clutter and take away from the purpose of simplified examples IMO). E.g. for some of the examples I've submitted I have an associated non-trivial <code>*_test.go</code> file and if someone else wanted to cleanup/change/add-to the example later it might be convenient for them if they had that too. —[[User:dchapes|dchapes]] ([[User talk:dchapes|talk]] | [[Special:Contributions/dchapes|contribs]]) 15:15, 3 September 2014 (UTC)
:::You can always add subpages. If you just go to http://rosettacode.org/wiki/task_name/Go/whatever_test.go you can create the page, add the text of your test file, and then add a link on the main Go example. We already make subpages for long examples (e.g. [[Pythagorean triples/Java/Brute force primitives]]) so it's not out of the ordinary. Putting links on the task pages to separate pages with more detailed information sounds like a great way to let people dig deeper if they so choose. --[[User:Mwn3d|Mwn3d]] ([[User talk:Mwn3d|talk]]) 15:45, 3 September 2014 (UTC)
| |||