Re: JUnit-BDD
David Saff <[email protected]> Tue, 29 Apr 2014 20:07:02 -0400
| Newsgroups | gmane.comp.java.junit.user |
|---|---|
| Message-ID | <CALrw-PwioE63rr6qcAf6Y97bj9QMPHyvdzSFy9SrCVi-EgzoDQ@mail.gmail.com> |
Just catching up on this thread. No, I think that lambdas represent more gracefully an idea (a nameable, referenceable chunk of code) that JUnit had previously needed to represent somewhat less elegantly by (ab-)using things like annotations and reflection+special-naming. But there are still applications for which annotations make sense, including aiding code analysis (@Nullable, @VisibleForTesting, @Override) and dynamic dependency injection (if you like that kind of thing). David On Wed, Apr 23, 2014 at 6:11 AM, <[email protected]> wrote: > > > hmmm... I'm curious... in the Scala world does the fundamental Annotation > construct give way to the Lambda construct? Or is that too broad of a > statement to be useful for future planning? > > Asked another way, do Lambdas represent the potential replacement of > Annotations in Java? > > >