LJC Lambdas Hackday

[David Conrad]

Type inference only happens at compile time, and once types are inferred,
the usual static type checking takes place. At run time, all the usual type
safety is there.

At least, that is my understanding.

If you really want to make Java safer, pressure them to reify generics and
get rid of that awful co- (or is it contra-?) variance on arrays. :)

David
 On Jun 4, 2012 5:47 PM, "Ben Evans" <benjamin.john.evans at gmail.com> wrote:

> On Mon, Jun 4, 2012 at 3:51 PM, Brian Goetz <brian.goetz at oracle.com>
> wrote:
> >
> > The problem with hacking type inference is that it is an endless loop of:
> >
> >  - Someone finds a case where type inference fails, but the right answer
> is "obvious"
> >  - Endless machinations and distortions ensue to try and make that case
> "go away"
> >  - Go to step 1
>
> Whilst in parallel, the following timebomb is waiting to go off:
>
> Some combination of type inference features provides an undesired,
> non-obvious result.
>
> If not caught in time, the language degenerates into something in
> which one can only produce unmaintainable crap.
>
> Type inference is a real "repent at leisure" part of the spec.
>
> Thanks,
>
> Ben
>