For more flexibility in NCrystal-Prompt/Cinema usage, Prompt should use a virtual NCrystal API like what was recently done for OpenMC in openmc-dev/openmc#3328
To do this, @xxcai1 must first identify the exact NCrystal functionality used in the C++ layer of Prompt, and then we must create a dedicated virtual API header.
On the NCrystal side, the work can happen in a PR, while we ensure that the chosen virtual API actually will work with prompt (since we support virtual APIs ~forever, we want to double check that it works before publishing it in an NCrystal release).
Of course the PR will depend on and modify #250 #249.
For more flexibility in NCrystal-Prompt/Cinema usage, Prompt should use a virtual NCrystal API like what was recently done for OpenMC in openmc-dev/openmc#3328
To do this, @xxcai1 must first identify the exact NCrystal functionality used in the C++ layer of Prompt, and then we must create a dedicated virtual API header.
On the NCrystal side, the work can happen in a PR, while we ensure that the chosen virtual API actually will work with prompt (since we support virtual APIs ~forever, we want to double check that it works before publishing it in an NCrystal release).
Of course the PR will depend on and modify #250 #249.