This feature request proposes an implementation of NonNativePointVar, which extends NonNativeFieldVar to points.
Problem Definition
I thought that we previously decided to rename nonnative to field_simulation and I sort of like the latter (as you can see, I have been widely using field simulation when talking about nonnative field vars".
I see that we stick to the old one that is more established.
There seems to be a rising demand to use nonnative tools in production. The potential benefit of it is that it may help developers to do nonnative SW, TE, and M points in a more unified way.
Proposal
NonNativePointVar would likely just be a "C++ STL"-like wrapper to NonNativePointVar.
Summary
This feature request proposes an implementation of NonNativePointVar, which extends NonNativeFieldVar to points.
Problem Definition
I thought that we previously decided to rename
nonnativetofield_simulationand I sort of like the latter (as you can see, I have been widely using field simulation when talking about nonnative field vars".I see that we stick to the old one that is more established.
There seems to be a rising demand to use nonnative tools in production. The potential benefit of it is that it may help developers to do nonnative SW, TE, and M points in a more unified way.
Proposal
NonNativePointVar would likely just be a "C++ STL"-like wrapper to NonNativePointVar.
For Admin Use