Javadoc (b116) lacks @FunctionalInterface on Observer signature

[Zhong Yu]

The chance seems very small that one could accidentally add an
abstract method to an interface (without being hit by lots of
compilation errors else where).

On Fri, Nov 22, 2013 at 11:52 AM, Brian Goetz <brian.goetz at oracle.com> wrote:
>> I still have no idea how the annotation is supposed to help us. Can
>> anyone provide a concrete use case for @FunctionalInterface?
>
>
> It captures design intent; the compiler assists you by enforcing that design
> intent (erroring if the class has more than one abstract method.)  Like the
> @Override annotation.