A disclaimer or two for Optional

[Joe Bowbeer]

I think the note should instruct users to refrain from
applying value-unsafe operations to Optionals so that their programs can
benefit from more performant implementations in the future.

More carrot, less stick.

If Optionals become value types, I'm betting that the implementation will
identify when its safe to optimize, and will fallback to a slow but correct
path in other cases.



On Wed, Oct 23, 2013 at 11:49 AM, Doug Lea <dl at cs.oswego.edu> wrote:

> On 10/23/2013 01:08 PM, Remi Forax wrote:
>
>> Given the previous discussions, there is also a good chance that Optional
>> became
>> the new heroine.
>>
>>
> I can't decide if you meant heroine (femme héroïque) or heroin (opiacés)!
> Either way is best post yet on this thread.
>
> -Doug
>
>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/lambda-libs-spec-experts/attachments/20131023/0ab6eda2/attachment.html