Well to be exact, 'now' is a shortcut for (expires_in => 0) and 'never' is a shortcut for (expires_at => CHI_Max_Time). So it wouldn't make sense for either of these to be a value for expires_in.
Also, 'never' is already the default for a set, if you don't specify otherwise.
I can appreciate the desire for consistency, but every change has its risks and in this case, IMO, the benefit is so minor as to make it not worth the cost...
On Aug 2, 2012, at 3:25 AM, Steven Lee via RT wrote:
Show quoted text> Thu Aug 02 06:25:22 2012: Request 78733 was acted upon.
> Transaction: Ticket created by STEVENL
> Queue: CHI
> Subject: (No subject given)
> Broken in: 0.55
> Severity: Wishlist
> Owner: Nobody
> Requestors: STEVENL@cpan.org
> Status: new
> Ticket <URL:
https://rt.cpan.org/Ticket/Display.html?id=78733 >
>
>
> The 'expires_in' option for set(), add() and replace() allow the values
> 'now' and 'never'. But these values are not available for the default
> 'expires_in' at construction.
>
> It would be good if these options were consistent. Perhaps do the
> translation at the 'CHI::Types::Duration' type coercion so that it is
> available anywhere the option is available.
RT for rt.cpan.org