You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
joaander opened this issue
Nov 8, 2023
· 0 comments
Assignees
Labels
breakingChanges that will break API.complexA particularly complex or large project that involves significant amount of effort.hpmcHPMC componenttaskSomething needs to be done.
On trunk-major (later, close to the release of v5.0):
Remove CPP potential classes.
Port walls and harmonic external potentials to new framework.
Remove JIT framework.
Remove LLVM from CMake.
Remove all mentions of run time compile potentials from the documentation.
Move all external hpmc potentials to hoomd.hpmc.external
Port muVT and SDF square well tests.
Motivation and context
The LLVM run time compilation code path is very costly to maintain. Using CPPPotential requires that users write C++ code regardless, so asking them to compile it is not a significant additional burden.
The text was updated successfully, but these errors were encountered:
joaander
added
hpmc
HPMC component
breaking
Changes that will break API.
task
Something needs to be done.
complex
A particularly complex or large project that involves significant amount of effort.
labels
Nov 8, 2023
breakingChanges that will break API.complexA particularly complex or large project that involves significant amount of effort.hpmcHPMC componenttaskSomething needs to be done.
Description
On
trunk-minor
:On
trunk-major
(later, close to the release of v5.0):hoomd.hpmc.external
Motivation and context
The LLVM run time compilation code path is very costly to maintain. Using
CPPPotential
requires that users write C++ code regardless, so asking them to compile it is not a significant additional burden.The text was updated successfully, but these errors were encountered: