hg: mlvm/mlvm/hotspot: 2 new changesets
Changeset: b4050524c2ff Author:Lukas Stadler Date: 2012-07-26 17:10 +0200 URL: http://hg.openjdk.java.net/mlvm/mlvm/hotspot/rev/b4050524c2ff coro: updated patch, new coro-simple version - coro-meth.patch + coro-simple.patch - coro-standalone.patch ! coro.patch ! series Changeset: 3bd88fb254b4 Author:Lukas Stadler Date: 2012-07-26 17:12 +0200 URL: http://hg.openjdk.java.net/mlvm/mlvm/hotspot/rev/3bd88fb254b4 merge ___ mlvm-dev mailing list mlvm-dev@openjdk.java.net http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
hg: mlvm/mlvm/jdk: 2 new changesets
Changeset: 1bb873eba051 Author:Lukas Stadler Date: 2012-07-25 14:19 +0200 URL: http://hg.openjdk.java.net/mlvm/mlvm/jdk/rev/1bb873eba051 fix meth-7177472.patch for recent changes in meth-lazy-7023639.patch ! meth-7177472.patch Changeset: 90c60ec5aba4 Author:Lukas Stadler Date: 2012-07-26 17:14 +0200 URL: http://hg.openjdk.java.net/mlvm/mlvm/jdk/rev/90c60ec5aba4 coro: updated patch, new coro-simple version + coro-simple.patch ! series ___ mlvm-dev mailing list mlvm-dev@openjdk.java.net http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
Re: MethodHandle.bindTo() only for reference types?
On 07/26/2012 11:50 AM, Aleksey Shipilev wrote: > Hi John, > > On 07/24/2012 11:02 PM, John Rose wrote: >> On Jul 24, 2012, at 11:09 AM, Attila Szegedi wrote: >> MethodHandle.bind is a less-general primitive. The general API is >> insertArguments. >> >> Good 292 support for primitives requires a signature-polymorphic API. >> >> Therefore, we have been considering adding something like this, to fill >> functionality not covered by bind and insertArguments: > Thanks for thinking forward on this. But let's get back to the original > issue: inconsistent API between MH.bindTo() and MHs.insertArguments(). > If the latter boxes primitive values, why not to allow the former to do > the same? Albeit it is not "a good support for primitives", but this is > the consistency improvement. The idea that that bindTo() should be used as Attila said when you want to de-virtualize a method by fixing the receiver to a particular object. The idea is that when you see bindTo() in a code you know the intent of the programmer without having to track precisely which parameter is bound with which value. > > Thanks, > Aleksey. cheers, Rémi ___ mlvm-dev mailing list mlvm-dev@openjdk.java.net http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
Re: MethodHandle.bindTo() only for reference types?
Hi John, On 07/24/2012 11:02 PM, John Rose wrote: > On Jul 24, 2012, at 11:09 AM, Attila Szegedi wrote: > MethodHandle.bind is a less-general primitive. The general API is > insertArguments. > > Good 292 support for primitives requires a signature-polymorphic API. > > Therefore, we have been considering adding something like this, to fill > functionality not covered by bind and insertArguments: Thanks for thinking forward on this. But let's get back to the original issue: inconsistent API between MH.bindTo() and MHs.insertArguments(). If the latter boxes primitive values, why not to allow the former to do the same? Albeit it is not "a good support for primitives", but this is the consistency improvement. Thanks, Aleksey. signature.asc Description: OpenPGP digital signature ___ mlvm-dev mailing list mlvm-dev@openjdk.java.net http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
