I don't know if it's been proposed before, but I think any implementation
would necessarily be inefficient.
I imagine such an iterator would need to produce objects of type Pair.
This would lead to a lot of allocation and could create garbage collection
pressure. The same functionality can be achie
I think this is a useful addition, but I wonder if these new APIs are
misnamed: StopWatch::test doesn't actually test, nor does StopWatch::accept
consume. Instead, these all wrap lambdas in a timed version of the same
type. (There's probably some lambda calculus terminology for this.)
I'd propose
I agree with Gary. If an object is exposing sensitive data in its
toString() then the problem should be fixed at the source.
Peter
On Tue, Sep 3, 2024, 11:04 AM Gary D. Gregory wrote:
> I appreciate the intent but this feels like bad solution. If a toString()
> method return a password, then t
This feels like it might have been more useful pre-Java 8. Why not use a
lamda function, which would permit arbitrary string transformations?
/peter
On Thu, Feb 22, 2018, 7:42 PM Gary Gregory wrote:
> On Thu, Feb 22, 2018 at 4:27 PM, sebb wrote:
>
> > On 22 February 2018 at 23:15, Gary Gregory
This could be solved if it were possible to force javac to generate bridge
methods. There's an extension which would allow that here:
https://github.com/infradna/bridge-method-injector, but I suspect it would
complicate the build process quite a bit.
On Thu, Mar 29, 2018 at 4:48 PM sebb wrote:
>
