- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
The state of Scala optional
Mon, 2012-01-16, 15:23
From what I've figured out from github you, Paul and Jamie, seem to be
the main contributors of the Scala `optional` library. What's the
current state of it? Is there a 2.9.1 build published somewhere?
Tue, 2012-01-17, 09:41
#2
Re: The state of Scala optional
Ok, thanks for the info, this makes sense. So we can't rely on
optional for scala 2.9.1.
Johannes
On Tue, Jan 17, 2012 at 4:39 AM, Paul Phillips wrote:
>
>
> On Mon, Jan 16, 2012 at 6:22 AM, Johannes Rudolph
> wrote:
>>
>> From what I've figured out from github you, Paul and Jamie, seem to be
>> the main contributors of the Scala `optional` library. What's the
>> current state of it? Is there a 2.9.1 build published somewhere?
>
>
> There's some monkey in the ointment. Remember how everyone got all mad when
> we released 2.9.0 because they couldn't figure out what was in their
> Option[Int]s like they could in 2.8? That's also how optional did its magic.
> So it's sidelined at the moment. It could be made to work in a variety of
> ways but since I have no time for it I don't expect to touch it until after
> we ship reflection.
>
Tue, 2012-01-17, 12:31
#3
Re: The state of Scala optional
> There's some monkey in the ointment. Remember how everyone got all mad
> when we released 2.9.0 because they couldn't figure out what was in their
> Option[Int]s like they could in 2.8?
I don't remember that, and you made me curious. Is there a discussion on
a list somewhere?
Tue, 2012-01-17, 12:41
#4
RE: Re: The state of Scala optional
A sad day indeed :-(
> To: scala-debate [at] googlegroups [dot] com
> From: hupel [at] in [dot] tum [dot] de
> Subject: [scala-debate] Re: The state of Scala optional
> Date: Tue, 17 Jan 2012 12:23:52 +0100
>
> > There's some monkey in the ointment. Remember how everyone got all mad
> > when we released 2.9.0 because they couldn't figure out what was in their
> > Option[Int]s like they could in 2.8?
>
> I don't remember that, and you made me curious. Is there a discussion on
> a list somewhere?
>
Welcome to Scala version 2.9.1.final (Java HotSpot(TM) Server VM, Java 1.6.0_18).Type in expressions to have them evaluated.Type :help for more information.
scala> List(Some(1), None, Some(2))res0: List[Option[Int]] = List(<<NOT TELLING>>, <<NOT TELLING>> , <<NOT TELLING>> )
> To: scala-debate [at] googlegroups [dot] com
> From: hupel [at] in [dot] tum [dot] de
> Subject: [scala-debate] Re: The state of Scala optional
> Date: Tue, 17 Jan 2012 12:23:52 +0100
>
> > There's some monkey in the ointment. Remember how everyone got all mad
> > when we released 2.9.0 because they couldn't figure out what was in their
> > Option[Int]s like they could in 2.8?
>
> I don't remember that, and you made me curious. Is there a discussion on
> a list somewhere?
>
Tue, 2012-01-17, 14:31
#5
Re: Re: The state of Scala optional
On Tue, Jan 17, 2012 at 12:23 PM, Lars Hupel <hupel [at] in [dot] tum [dot] de> wrote:
https://issues.scala-lang.org/browse/SI-5255
http://www.scala-lang.org/node/8888
-jason
> There's some monkey in the ointment. Remember how everyone got all mad
> when we released 2.9.0 because they couldn't figure out what was in their
> Option[Int]s like they could in 2.8?
I don't remember that, and you made me curious. Is there a discussion on
a list somewhere?
https://issues.scala-lang.org/browse/SI-5255
http://www.scala-lang.org/node/8888
-jason









On Mon, Jan 16, 2012 at 6:22 AM, Johannes Rudolph <johannes [dot] rudolph [at] googlemail [dot] com> wrote:
There's some monkey in the ointment. Remember how everyone got all mad when we released 2.9.0 because they couldn't figure out what was in their Option[Int]s like they could in 2.8? That's also how optional did its magic. So it's sidelined at the moment. It could be made to work in a variety of ways but since I have no time for it I don't expect to touch it until after we ship reflection.