Timeline for Non-discriminating Programming
Current License: CC BY-SA 3.0
23 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2020 at 9:04 | history | edited | CommunityBot | Commonmark migration | |
| Mar 2, 2018 at 9:00 | history | edited | Olivier Grégoire | CC BY-SA 3.0 | Add a relevant change I used. |
| Mar 2, 2018 at 8:26 | comment | added | Olivier Grégoire | Sorry for the mess I put here! xD Hint for further golfing: start from version at 165 bytes, golf that, then use @KevinCruyssen's analysis of my mess to remove the comments. Be ready to spend time on it! | |
| Mar 1, 2018 at 20:44 | comment | added | praosylen | @KevinCruijssen Sorry, missed the edit. I can't see any way to do that now, but maybe there still is one. | |
| Mar 1, 2018 at 20:40 | comment | added | Kevin Cruijssen | @AidanF.Pierce Hmm, might indeed be possible. Only problem in the current implementation where we increase the flag x[0] is that byte can only hold up to 127, and will wrap-around (127 + 1 = -128). So the check if the flag is larger than 0 in the end will return false because 2220 is too big. But perhaps there is indeed a way to remove those 333s using the three leftover 2s. | |
| Mar 1, 2018 at 20:30 | comment | added | praosylen | All 3s should be able to be removed by using "2220", also. Untested, though. | |
| Mar 1, 2018 at 20:30 | history | edited | Kevin Cruijssen | CC BY-SA 3.0 | added 1445 characters in body |
| Mar 1, 2018 at 19:02 | comment | added | Olivier Grégoire | 160 bytes (proof). Very likely more golfable. | |
| Mar 1, 2018 at 18:59 | comment | added | PunPun1000 | Since you only care about printable ascii, making the array size 222 works in theory to remove the 3s, but in practice that runs into an overflow issue due to the byte array which 3333 manages to cleanly avoid since it's 13*256+5 (I was looking into this before you changed it back to a byte array) Didn't know if there was anything you could do with that information | |
| Mar 1, 2018 at 16:48 | comment | added | Kevin Cruijssen | @OlivierGrégoire Isn't it possible to change the char-count from 6 to 5 somehow like I did in my current 165-bytes answer? | |
| Mar 1, 2018 at 16:44 | comment | added | Olivier Grégoire | Closest I am to 162 characters (161 characters). I'm trying to remove the comment, but I still need to put a comma somewhere. I just can't find any place. | |
| Mar 1, 2018 at 16:34 | history | edited | Kevin Cruijssen | CC BY-SA 3.0 | added 2250 characters in body |
| Mar 1, 2018 at 15:59 | history | edited | Kevin Cruijssen | CC BY-SA 3.0 | added 139 characters in body |
| Mar 1, 2018 at 15:55 | comment | added | Olivier Grégoire | The change can still apply to save 6 bytes. | |
| Mar 1, 2018 at 15:55 | comment | added | Kevin Cruijssen | @OlivierGrégoire Sorry, I'm already at 174 :) But will see if your trick can still be applied. | |
| Mar 1, 2018 at 15:55 | history | edited | Kevin Cruijssen | CC BY-SA 3.0 | added 69 characters in body |
| Mar 1, 2018 at 15:54 | comment | added | Olivier Grégoire | 180 bytes: changed all < into >. | |
| Mar 1, 2018 at 15:41 | history | edited | Kevin Cruijssen | CC BY-SA 3.0 | deleted 2 characters in body |
| Mar 1, 2018 at 15:32 | history | edited | Kevin Cruijssen | CC BY-SA 3.0 | typos |
| Mar 1, 2018 at 15:09 | history | edited | Kevin Cruijssen | CC BY-SA 3.0 | added 108 characters in body |
| Mar 1, 2018 at 14:59 | history | edited | Kevin Cruijssen | CC BY-SA 3.0 | added 1968 characters in body |
| Mar 1, 2018 at 14:53 | history | edited | Kevin Cruijssen | CC BY-SA 3.0 | added 1968 characters in body |
| Mar 1, 2018 at 14:44 | history | answered | Kevin Cruijssen | CC BY-SA 3.0 |