Timeline for Project Euler #12 runs very slowly
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 10, 2020 at 13:24 | history | edited | CommunityBot |
Commonmark migration
|
|
| Apr 13, 2017 at 12:40 | history | edited | CommunityBot |
replaced http://codereview.stackexchange.com/ with https://codereview.stackexchange.com/
|
|
| May 3, 2015 at 19:30 | history | edited | Mast♦ | CC BY-SA 3.0 |
deleted 77 characters in body
|
| May 3, 2015 at 19:23 | history | edited | Mast♦ | CC BY-SA 3.0 |
added 188 characters in body
|
| May 3, 2015 at 19:18 | comment | added | Mast♦ |
@GarethRees I assume all code is written to last. After all, what's the point in reviewing if it isn't supposed to last? The code will hit an infinite loop at n = 0, so this situation should be asserted.
|
|
| May 3, 2015 at 19:05 | comment | added | Mast♦ |
Using assert would be a good choice. They are meant for situations which should not happen.
|
|
| May 3, 2015 at 18:30 | comment | added | help needed | Thank you for the review. How can I prevent the loop hangup problem? | |
| May 3, 2015 at 18:04 | history | answered | Mast♦ | CC BY-SA 3.0 |