My understanding is that DJL depends on MXNet, so if you want to bring JNA from
DJL into MXNet, it will create circular dependency as a 3rdparty module. In
terms of stability, I was referring to the development of code base rather than
the performance.
--
You are receiving this because you are
There is no code for JNA, everything is generated. It ensure the general
standard and minimum layer in C to avoid error and mistakes.
About JNA, you can find more information here:
[jnarator](https://github.com/awslabs/djl/tree/master/mxnet/jnarator). We build
an entire project for the jna gene
@lanking520 would it create circular dependency? and how stable is the JNA and
what changes are expected? it would be great if you could share a pointer on
the JNA code to help clarify these concerns.
--
You are receiving this because you are subscribed to this thread.
Reply to this email direc
@szha For option 4, I would recommend to consume the JNA layer as a submodule
from DJL. I am not sure if this is recommendation serves as "add a dependency
in mxnet".
There are two key reason that support for that:
1. DJL moves really fast and we can quickly change the JNA layer whenever in
ne
