<meta charset="utf-8"><span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif; font-size: medium; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; "><pre style="font-family: monospace; margin-left: 3em; font-size: 12px; ">
"In fact 1 (integer one) is by definition NOT a prime number
see <a href="http://primes.utm.edu/" style="color: rgb(0, 0, 96); ">http://primes.utm.edu/</a>"</pre><pre style="font-family: monospace; margin-left: 3em; font-size: 12px; "><br></pre><pre style="font-family: monospace; margin-left: 3em; font-size: 12px; ">
Yea, I had a feeling somebody was going to say this. As a non-math person, it seems obvious to me that 1 would be a prime. That it is a prime doesn't change for me that the old design of isPrime in 3.10.2 was not to my liking. If I give isPrime a list of numbers to check. It should give a judgement on whether it is or isn't prime. It shouldn't say "I'll stop on 1, because.... it's not a prime!" 4 isn't a prime either. Should it stop there? Clearly the designers of the new Trunk isPrime didn't think so. The old implementation created confusion for me, where, rightfully, I don't think there should have been any.</pre>
<pre style="font-family: monospace; margin-left: 3em; font-size: 12px; "><br></pre><pre style="font-family: monospace; margin-left: 3em; font-size: 12px; ">Chris
<br></pre></span>