[
https://issues.apache.org/jira/browse/TAP5-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17652777#comment-17652777
]
ASF subversion and git services commented on TAP5-2743:
-------------------------------------------------------
Commit 0a644287cdc21b8b271b169f244ff3fbe0032f07 in tapestry-5's branch
refs/heads/TAP5-2743 from Ben Weidig
[ https://gitbox.apache.org/repos/asf?p=tapestry-5.git;h=0a644287c ]
TAP5-2743: add "ifSet" to PerThreadValue<T>
> PerThreadValue<T> should provide more convenience methods
> ---------------------------------------------------------
>
> Key: TAP5-2743
> URL: https://issues.apache.org/jira/browse/TAP5-2743
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-ioc
> Reporter: Ben Weidig
> Assignee: Ben Weidig
> Priority: Trivial
>
> The type org.apache.tapestry5.ioc.services.PerThreadValue<T> should provide
> more convenience methods like Map does, e. g.:
> * {{T computeIfAbsent(Supplier<? super T> fn)}}
> * {{TÂ }}{{computeIfPresent(Function<? super T, ? extends T> fn)}}
> * {{{}T compute{}}}{{{}(Function<? super T, ? extends T> fn){}}}{{{}{}}}
> I believe these methods would simplify using PerThreadValue and they should
> be implementable with default methods directly on the interface.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
