On 27 Feb 2013, at 13:00, Andy Dennie wrote:
>
> Replying via email since I can't seem to find this comment on 
> github...
>
> If you're referring to the fact that there's a missing .isTrue() at 
> the
> end of that line, I fixed that yesterday.
>
> Or are you questioning the purpose of the test?

No, I'm saying that this mistake was an easy one to make and is a 
down-side of fluent APIs like Fest or Truth, and it might be good to use 
something like error-prone to detect and make compile errors a 
purely-no-op statements like

```
assertThat(aBoolean); // FEST
ASSERT.that(aBoolean); // Truth
```

since they obviously need isTrue() to "turn the crank" on the fluent 
api.  So they're in all cases errors where the result of the method 
isn't captured into a variable.

Just a tooling comment, since we do use a fluent API testing framework.  
I'll take it up with the error-prone team and Alex Ruiz (of FEST) and 
see if we can't get some of these obvious cases to be impossible to 
compile.

cheers,
Christian.

Christian Gruber :: Google, Inc. :: Java Core Libraries :: Dependency 
Injection
email: cgruber@google.com :::: mobile: +1 (646) 807-9839