-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Polygon stdlib function #4300
Polygon stdlib function #4300
Conversation
QA Wolf here! As you write new code it's important that your test coverage is keeping up. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@adamchalmers, is it possible to implement this stdlib function in KCL? I know we have some infrastructure for that like the below, but I don't think we actually use it.
@guptaarnav, I don't want to make you redo this PR. I only thought of this now. Our internal users wrote an |
@jtran, i'm not sure i understand, i thought my PR was implementing polygon as a stdlib function in kcl. what's different in what you're alluding to? is the internal p.s. i don't mind redoing the PR as long i understand what should be changed |
It's theoretically possible to implement a KCL stdlib function in KCL, as opposed to in Rust. I.e. the function is actually implemented with KCL code. There's some code to support this, like what I linked above. But I don't think we actually use it. So there may be more missing. If there's a lot missing (I'm guessing there is), it's probably not worth going that route now. |
Succeeded by #4341 |
Implements polygon in the kcl stdlib to close #4261
There seems to be an issue with edge/face selection of the polygon, but I don't think its related to this implementation (please correct me if i'm wrong). Upon looking into what commands are sent via the debug console, it appears that when selecting an edge/face, the engine selects that edge/face, then immediately clears the selection, then consistently selects a specific edge/face instead of the targeted edge/face. This seems to be happening for any selection on other entities, as well, i.e. when the user selects some entity, the engine will select, then clear selection, then reselect in rapid succession.