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
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.
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged
Contributor assigned/self-assigned
The text was updated successfully, but these errors were encountered:
Summary
This feature request proposes an implementation of NonNativePointVar, which extends NonNativeFieldVar to points.
Problem Definition
I thought that we previously decided to rename
nonnative
tofield_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.
For Admin Use
The text was updated successfully, but these errors were encountered: