Thanks Reynold, that helps a lot. I'm glad you're involved with that Google
Doc community effort. I think it's because of that doc that the JEP's
wording and scope changed for the better since it originally got
introduced.
Marek
On Fri, Aug 21, 2015 at 11:18 AM, Reynold Xin wrote:
> I'm actuall
I'm actually somewhat involved with the Google Docs you linked to.
I don't think Oracle will remove Unsafe in JVM 9. As you said, JEP 260
already proposes making Unsafe available. Given the widespread use of
Unsafe for performance and advanced functionalities, I don't think Oracle
can just remove
On 21 Aug 2015, at 05:29, Marek Kolodziej
mailto:mkolod@gmail.com>> wrote:
I doubt that Oracle would want to make life difficult for everyone. In addition
to Spark's code base, projects such as Akka, Cassandra, Hibernate, Netty, Neo4j
and Spring (among many others) depend on Unsafe. Still,
Hello,
I attended the Tungsten-related presentations at Spark Summit (by Josh
Rosen) and at Big Data Scala (by Matei Zaharia). Needless to say, this
project holds great promise for major performance improvements.
At Josh's talk, I heard about the use of sun.misc.Unsafe as a way of
achieving some
