This page is no longer maintained — Please continue to the home page at www.scala-lang.org

Why isn't Option @specialized?

2 replies
nilskp
Joined: 2009-01-30,
User offline. Last seen 1 year 27 weeks ago.

It seems like a prime candidate.

extempore
Joined: 2008-12-17,
User offline. Last seen 35 weeks 3 days ago.
Re: Why isn't Option @specialized?

On Wed, Nov 9, 2011 at 12:53 PM, Nils Kilden-Pedersen wrote:
> It seems like a prime candidate.

https://issues.scala-lang.org/browse/SI-5005
"@specialize vs. @inline: @specialize wins (unnecessarily)"

"a) one of the few classes I would specialize with no reservations is
Option and b) we cannot even consider specializing Option unless this
is fixed, because we would be gifted with hundreds of getOrElse
closure objects which are presently eliminated."

nilskp
Joined: 2009-01-30,
User offline. Last seen 1 year 27 weeks ago.
Re: Why isn't Option @specialized?
On Wed, Nov 9, 2011 at 7:00 PM, Paul Phillips <paulp [at] improving [dot] org> wrote:
On Wed, Nov 9, 2011 at 12:53 PM, Nils Kilden-Pedersen <nilskp [at] gmail [dot] com> wrote:
> It seems like a prime candidate.

https://issues.scala-lang.org/browse/SI-5005
"@specialize vs. @inline: @specialize wins (unnecessarily)"

"a) one of the few classes I would specialize with no reservations is
Option and b) we cannot even consider specializing Option unless this
is fixed, because we would be gifted with hundreds of getOrElse
closure objects which are presently eliminated."

Thanks. I hope it'll get fixed :-)

Copyright © 2012 École Polytechnique Fédérale de Lausanne (EPFL), Lausanne, Switzerland