Timeline for Sandbox for Proposed Challenges
Current License: CC BY-SA 4.0
29 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2020 at 9:03 | history | edited | CommunityBot |
Commonmark migration
|
|
| Sep 23, 2019 at 14:09 | history | edited | simonalexander2005 | CC BY-SA 4.0 |
added 791 characters in body
|
| May 2, 2018 at 13:12 | comment | added | simonalexander2005 | @user202729 would you compress by byte also then? | |
| May 2, 2018 at 8:48 | comment | added | user202729 | @simonalexander2005 I find it (compress by character, score by byte) unnecessarily complex. | |
| Apr 29, 2018 at 11:16 | comment | added | l4m2 | Brute force is the best | |
| Apr 27, 2018 at 12:56 | history | edited | simonalexander2005 | CC BY-SA 3.0 |
added 21 characters in body
|
| Apr 27, 2018 at 12:38 | comment | added | simonalexander2005 |
@user202729 The scoring is a byte count; just the program uses characters to compress/decompress. The compression ratio for someone using a golfing language is likely to be very poor, compared with say someone using ><> or even VB.NET - but it's the job of the coder to decide which language will get them the best score for the question; right?
|
|
| Apr 18, 2018 at 8:59 | comment | added | user202729 | I still feel that it's open to abuse. We had reasons to score by byte count instead of character count. | |
| Apr 18, 2018 at 8:52 | comment | added | simonalexander2005 | @user202729 but it will be convertible to something, using a custom code-page of some sort. Even if it's UTF-16 or some other encoding, right? | |
| Apr 17, 2018 at 15:29 | comment | added | user202729 | The "program" is most likely an arbitrary byte string, and thus it may be invalid UTF-8. | |
| Apr 17, 2018 at 13:51 | comment | added | simonalexander2005 | @user202729 could you expand on what issues would occur? I'm not quite sure I get what the issues could be here | |
| Apr 12, 2018 at 15:56 | comment | added | user202729 | Are you sure that you want to work on characters and not bytes (and thus facing multiple complicated codepage issues)? Especially consider that the program itself is compressed. | |
| Apr 12, 2018 at 15:42 | comment | added | simonalexander2005 | @Leo helpful, thanks. Updated - hope it's clear | |
| Apr 12, 2018 at 15:42 | history | edited | simonalexander2005 | CC BY-SA 3.0 |
added 264 characters in body
|
| Apr 11, 2018 at 22:22 | comment | added | Leo |
One possibility would be letting people choose the separator character (instead of fixing it as |), and requiring that a submission works on inputs consisting of all the required characters plus all the characters contained in the submitted source. This should give enough freedom to make solutions possible in more languages.
|
|
| Apr 11, 2018 at 13:29 | comment | added | simonalexander2005 |
@Leo yes, it does limit the source somewhat, doesn't it? What would be better then? - increasing the range of characters allowed to allow any character except, say, | (and the dictionary has to key on missing characters only); or keep the limited input and also limit people's source?
|
|
| Apr 11, 2018 at 9:38 | comment | added | Leo | How would you score a submission containing characters different from the ones allowed in input? | |
| Apr 11, 2018 at 9:26 | history | edited | simonalexander2005 | CC BY-SA 3.0 |
deleted 66 characters in body
|
| Apr 11, 2018 at 9:25 | comment | added | simonalexander2005 | @Nathaniel Good to know, thanks | |
| Apr 11, 2018 at 7:54 | comment | added | N. Virgo | Mostly irrelevant nitpick: no lossless compression algorithm is guaranteed to make its input smaller, a result often known as the "no free lunch theorem." | |
| Apr 10, 2018 at 13:35 | history | edited | simonalexander2005 | CC BY-SA 3.0 |
added 1 character in body
|
| Apr 4, 2018 at 12:37 | history | edited | simonalexander2005 | CC BY-SA 3.0 |
added 102 characters in body
|
| Apr 3, 2018 at 15:21 | history | edited | simonalexander2005 | CC BY-SA 3.0 |
edited body
|
| Apr 3, 2018 at 15:13 | history | edited | simonalexander2005 | CC BY-SA 3.0 |
added 573 characters in body
|
| Apr 3, 2018 at 15:03 | history | edited | simonalexander2005 | CC BY-SA 3.0 |
added 1 character in body
|
| Apr 3, 2018 at 14:53 | comment | added | simonalexander2005 | @PeterTaylor I changed my mind half way through, sorry fixed now | |
| Apr 3, 2018 at 14:53 | history | edited | simonalexander2005 | CC BY-SA 3.0 |
deleted 10 characters in body
|
| Apr 3, 2018 at 14:37 | comment | added | Peter Taylor |
I'm confused: not only does the output format explanation use = but the question explicitly says that = is reserved, and yet none of the examples use it.
|
|
| Apr 3, 2018 at 14:03 | history | answered | simonalexander2005 | CC BY-SA 3.0 |