On 23 September 2015 at 12:32, Hugues Bruant <hugues at aerofs.com> wrote:
> On Wed, Sep 23, 2015 at 12:00 AM, Rowan Worth <rowanw at dugeo.com> wrote: > > > Has many possible explanations. > > I can't think of any that is consistent with the Java specification. > Yeah fair enough, SIndex looks watertight. It's still possible for some other code to change _i through reflection but (a) I presume you would know if you were doing something like that and (b) it wouldn't explain the null SIndex capture. in some cases the SIndex captured inside the first lambda > (UPDATE statement) appeared to be null even though it wasn't null in the > enclosing scope (setVersion_) Interesting (and disturbing) result. Is this with Oracle's java compiler? -Rowan
