Timeline for Shortest auto-destructive loop
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 12, 2017 at 7:21 | history | edited | Dennis | CC BY-SA 3.0 |
added 8 characters in body
|
| Dec 27, 2016 at 22:22 | comment | added | Dennis | @MadPhysicist That is correct. This is a inherent problem with time limits though. Compliance depends very much on which machine the program is run. | |
| Dec 27, 2016 at 22:18 | comment | added | Mad Physicist | So will fail condition #5 on slow machine with lots of RAM? | |
| Dec 25, 2016 at 0:48 | history | edited | Dennis | CC BY-SA 3.0 |
added 7 characters in body
|
| Dec 24, 2016 at 0:43 | comment | added | tuskiomi | So every 2 years, we'll be able to execute another iteration | |
| Dec 24, 2016 at 0:40 | comment | added | Dennis | Jelly doesn't have an explicit memory limit, so whatever Python can address. Memory usage doubles with each iteration though, so this should exhaust all available memory rather quickly. | |
| Dec 24, 2016 at 0:09 | comment | added | tuskiomi | What is jelly's memory limits? | |
| Dec 23, 2016 at 22:28 | history | edited | Dennis | CC BY-SA 3.0 |
added 334 characters in body
|
| Dec 23, 2016 at 22:15 | history | answered | Dennis | CC BY-SA 3.0 |