-
Notifications
You must be signed in to change notification settings - Fork 75
Update fillet+chamfer with new API options #6745
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
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 ↗︎
|
CodSpeed Instrumentation Performance ReportMerging #6745 will not alter performanceComparing Summary
|
75072e0
to
ca93fb7
Compare
ca93fb7
to
8f7ef49
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My preference would be to not add strategy at all until after 1.0 and do it properly with an enum rather than add more string literal hacks. But if we think it is an essential feature then it's fine.
@settings(defaultLengthUnit = mm, kclVersion = 1.0) | ||
|
||
/// Try the fast but simple Basic strategy, and if that fails, try the slow and complex CSG strategy. | ||
export automatic = "automatic" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could these be all caps like the turns and maths constants?
@@ -71,6 +71,8 @@ export fn fillet( | |||
tolerance?: number(Length), | |||
/// Create a new tag which refers to this fillet | |||
tag?: tag, | |||
/// Which strategy should be used to perform this chamfer? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/// Which strategy should be used to perform this chamfer? | |
/// Which strategy should be used to perform this fillet? |
for _ in 0..num_extra_ids { | ||
extra_face_ids.push(exec_state.next_uuid()); | ||
} | ||
let strategy = strategy.unwrap_or_default(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should warn or error on a bad strategy, at the moment a typo in a string literal will silently use the default
closing in favor of #6750 |
Engine recently improved edge cuts (i.e. fillets/chamfers):
fillet(strategy = cutStrategy::basic)
instead.