Timeline for Sieve31, my sieve of Eratosthenes returning IEnumerable<int>
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:40 | history | edited | CommunityBot | replaced http://codereview.stackexchange.com/ with https://codereview.stackexchange.com/ | |
| Nov 11, 2015 at 15:21 | comment | added | Dan | I'm also informed by @EBrown that C# will implicitly throw OOM errors when you create objects of > 2GB in size unless you enable a flag, gcAllowVeryLargeObjects. | |
| Nov 11, 2015 at 15:19 | comment | added | Dan | @RickDavin consider that people give their reviews for free, you'd do well to be slightly less rude. This implementation appears to be O(n) which would mean that accessing int.MaxValue would require 4 billion bytes of memory, or 4GB of RAM - plus the extra array that OP has, which brings it to 8GB. Perhaps your PC just isn't up to scratch? :-) Even the wikipedia article acknowledges memory limitations as the prime issue with SoE. | |
| Aug 30, 2015 at 12:52 | comment | added | Rick Davin | I am the OP. Glad to see that you properly credited @EBrown. Despite that, I consider you answer to be poor and weak since it throws an out of memory exception for an upper limit of int.MaxValue. | |
| Aug 27, 2015 at 20:32 | history | edited | janos | CC BY-SA 3.0 | added 109 characters in body |
| Aug 27, 2015 at 20:31 | history | edited | t3chb0t | CC BY-SA 3.0 | added 197 characters in body |
| Aug 27, 2015 at 20:30 | history | edited | t3chb0t | CC BY-SA 3.0 | added 197 characters in body |
| Aug 27, 2015 at 20:19 | history | edited | t3chb0t | CC BY-SA 3.0 | added 157 characters in body |
| Aug 27, 2015 at 19:57 | history | answered | t3chb0t | CC BY-SA 3.0 |