From: Noah Gibbs <the.codefolio.guy@...>
Date: 2016-06-07T13:11:16-07:00
Subject: [ruby-dev:49648] Prime doesn't work as a Singleton because it has	no .new() method

--001a114ecf169eb33c0534b5ca15
Content-Type: text/plain; charset=UTF-8

I was looking at Bug #11953 (https://bugs.ruby-lang.org/issues/11953).

It looks like Prime is now a Singleton. But unfortunately, it has no .new()
method that works. The Singleton .instance() method requires .new().

This causes some code to fail, like the simple Prime test in Bug #11953.

Should Prime go back to tracking its instance internally with a member
variable, like it did before commit
d2487ed47587ec1cd1b456068e0af3ea0b39596d?

--001a114ecf169eb33c0534b5ca15
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I was looking at Bug #11953 (<a href=3D"https://bugs.ruby-=
lang.org/issues/11953">https://bugs.ruby-lang.org/issues/11953</a>).<div><b=
r></div><div>It looks like Prime is now a Singleton. But unfortunately, it =
has no .new() method that works. The Singleton .instance() method requires =
.new().</div><div><br></div><div>This causes some code to fail, like the si=
mple Prime test in Bug #11953.</div><div><br></div><div>Should Prime go bac=
k to tracking its instance internally with a member variable, like it did b=
efore commit=C2=A0<span style=3D"color:rgb(51,51,51);font-family:Consolas,M=
enlo,&quot;Liberation Mono&quot;,Courier,monospace;font-size:12px;white-spa=
ce:pre-wrap;background-color:rgb(250,250,250)">d2487ed47587ec1cd1b456068e0a=
f3ea0b39596d?</span></div><div><br></div></div>

--001a114ecf169eb33c0534b5ca15--