A syntax option (function types versus arrays)
howard.lovatt at gmail.com
Thu Mar 11 22:16:36 PST 2010
My understanding is that the JVM is free to optimize object creation
away as long as it can convince itself that the effect cannot be
observed, hence the escape analysis proposed that will stack allocate
instead of heap allocate.
On 12 March 2010 10:22, Alex Blewitt <alex.blewitt at gmail.com> wrote:
> On 11 Mar 2010, at 23:14, John Nilsson wrote:
> On Thu, Mar 11, 2010 at 11:58 PM, Howard Lovatt <howard.lovatt at gmail.com>
>> There is an advantage in spelling out that you have an expensive
>> operation in that people are more likely to be aware of a potential
>> problem and hence avoid it in the first place
> But it is only expensive if you assume a broken compiler or VM. There is
> nothing inherent in the language to suggest that it should be expensive.
> If you specify 'new' then the runtime VM is forced to lay out space for the
> new data as well as return a fresh instance:
> Next, space is allocated for the new class instance. Every time the
> expression is evaluated, a fresh object is created
> So by using the keyword 'new' - and assuming unchanged semantics in this
> area of the JLS - then you are going to at least cycle through the new
> generation even if the runtime JIT may be able to optimise it away in
> certain circumstances.
> However, if the keyword 'new' is not used then these issues do not apply.
More information about the lambda-dev