As a first experiment with it was trying to compare SoA vs AoS implementations of the same numerical method but didn't succeeded so far. As the c++ documentation is TBD... to get an idea on the general API design I used the one from Enoki's combined with the files available in the tests directory. Doing so I noticed that several files in the tests directory are not compiling (vector.cpp, dynamic.cpp, sphere.cpp).
The commented tests seems to use AoS style of coding and I wonder if you have plan to restore them, possibly by re-implementing currently missing features, or if it was decided not to go in this direction.
I am not sure to understand what you mean by AoS style coding. Could you maybe provide a code example of what you are trying to achieve in Dr.Jit? (e.g. in Enoki code, that's fine as well)
Hi,
Congratulation for the making of DrJit.
As a first experiment with it was trying to compare SoA vs AoS implementations of the same numerical method but didn't succeeded so far. As the c++ documentation is TBD... to get an idea on the general API design I used the one from Enoki's combined with the files available in the tests directory. Doing so I noticed that several files in the tests directory are not compiling (vector.cpp, dynamic.cpp, sphere.cpp).
The commented tests seems to use AoS style of coding and I wonder if you have plan to restore them, possibly by re-implementing currently missing features, or if it was decided not to go in this direction.
Regards,