Timeline for Loopholes that are forbidden by default
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 22 at 9:08 | comment | added | Kai Burghardt | +1: You write source code for humans. The fact that a computer will process your code is (almost) none of your business. Hence source code needs to remain legible for humans. | |
| Mar 8, 2017 at 6:14 | comment | added | Esolanging Fruit |
In addition, if you're doing a kolmogorov-complexity challenge in a language like ///, the only way to be competitive whatsoever is to compress the source code. If you can find a way to encode and then eval your code so that it's shorter than the normal algorithm, than good for you.
|
|
| Apr 13, 2015 at 14:27 | comment | added | Rainbolt | I do not think that this is a loophole. The default scoring is in bytes for good reason. If a challenge author deviates, then I'd assume they have a good reason for doing so. | |
| Apr 13, 2015 at 14:25 | comment | added | Optimizer |
This can be argued and extended to many other built-ins. Like Mathemetica's built in MandelbrotSetPlot to plot a mandelbrot set. I think the practice of questions themselves explicitly disallowing such compressions is the most favorable scenario and holds true for any such built-in, not just code compression ones
|
|
| S Apr 12, 2015 at 21:39 | history | answered | FUZxxl | CC BY-SA 3.0 | |
| S Apr 12, 2015 at 21:39 | history | made wiki | Post Made Community Wiki by FUZxxl |