stormofice

Hi, thanks for the review. I didn't use docstrings originally, as there was some discussion on whether we should use language specific documentation style comments at all, but I agree...

I think the main part would be creating a standardized testing format, as most of the examples currently don't have any tests associated to them (and if they do the...

I just did a quick check and noticed that 16/22 Julia files do write to standard output (mostly older ones), but changing them to write to a .dat file instead...

Now that I think about it, I would prefer outputting to stdout. In most languages it is easier to output directly to the console instead of a file (which leads...

> I executed the following in the `contents/` directory: > `find . -type f | sed -n 's/..*\.//p' | sort | uniq -c | sort -r` > This creates a...

After some discussion on discord, this is what has come out of it: - Standardizing code output is important for automatic testing - Labeled outputs are still important for human...

As per #864, we decided to use `[#]\n` instead of `\n` for more consisting formatting, which is easy to understand for humans and machines.

There was a previous discussion in #167 without a conclusive result, but it may contain relevant information.

The languages which I standardized already can be reviewed, however it would be good to gather some more implementations before the final review.

I am done with all the implementations which can be standardized properly (excluding esoteric and graphical languages). Clojure / Factor / Smalltalk / viml were not standardized, as I could...