document invokedynamic improvement authored by Frédéric Bapst's avatar Frédéric Bapst
...@@ -73,8 +73,9 @@ into richer number types, so that you can experiment, at a very low cost, some ...@@ -73,8 +73,9 @@ into richer number types, so that you can experiment, at a very low cost, some
beautiful models such as arbitrary precision numbers, interval computation, beautiful models such as arbitrary precision numbers, interval computation,
or even the marvelous automatic differentiation. or even the marvelous automatic differentiation.
See [§3](home#3-cojac-the-enriching-wrapper). This second tool is fun but still experimental (some See [§3](home#3-cojac-the-enriching-wrapper). This second tool is fun but still experimental (some
[limitations](home#52-issues-with-the-wrapper), [limitations](home#52-issues-with-the-wrapper) such as quite naive models implementation,
problems with Java8 lambdas, strong slowdown...). strong slowdown, poorly tested support for Java8 lambdas, problem when user-code
is "called back" from Java library...).
With COJAC you don't have to modify your source code or even recompile. All With COJAC you don't have to modify your source code or even recompile. All
the work is done at runtime, when your application gets instrumented on-the-fly. the work is done at runtime, when your application gets instrumented on-the-fly.
...@@ -592,8 +593,9 @@ when arrays of numbers are involved. ...@@ -592,8 +593,9 @@ when arrays of numbers are involved.
* We don't handle the "callbacks" from java library to user code when floating * We don't handle the "callbacks" from java library to user code when floating
point numbers are being passed around. point numbers are being passed around.
* We don't handle `invokedynamic` for the moment, so there are problems with * We have tried to handle `invokedynamic` (at least how Java8 compilers
java8 lambdas. use it), but it has not been thoroughly tested yet, so we expect some problems
with java8 lambdas.
* We don't handle the possible use of Java reflection (in case of method * We don't handle the possible use of Java reflection (in case of method
invocations via reflection, we don't apply the necessary transformations). invocations via reflection, we don't apply the necessary transformations).
... ...
......