Adam Gent

Yeah the support for null analysis in general at times appears to be dwindling (at other times it looks fine) and makes me sort of concerned that Stephan (stephan-herrmann) is...

I'm still learning Eclipse's NP analysis but I think eclipse not inferring that: ``` Stream = Stream.filter(Objects::nonNull); ``` is correct logic. This is because `nonNull` could be the inverse logic....

Sorry for the late reply. I'm still figuring out how the inference is done for Eclipse NP but from a purely type semantics and inverse logic I meant you could...

I guess Eclipse does additional null analysis on attached source libraries such that `requireNonNull` and `nonNull` are equivalent to inlining the conditional logic (ie `if o != null ... else/return`)....

@J-N-K Actually you are right about: ``` Stream = Stream.filter(Objects::nonNull); ``` I couldn't understand how the Objects.* methods could have complete null analysis. My understanding was just type based (ie...

Oh the ECA failed because I did the commit using github directly and it must have put the wrong email in.... It is such a trivial change.... I don't have...

Yes this was an oversight. There are some major updates that we have made in my company that have not been put back into the project. I'll follow up shortly.

The problem with the recursive dao idea is how do you know when to insert child objects or just associate? In my opinion and this is after dealing with hibernates...

You would subclass HtmlBuilder. ``` java public class MyBuilder extends HtmlBuilder { public T data(String custom, String value) { return attr("data-" + custom, value); } public T getSelf() { return...

Work for insert and update but not where clauses. The `where` clause will be difficult to do given the `where` builders are decoupled from object meta data.