{{ message }}
Deprecate point_at_t and document that a BezierSegment can be called - #30070
Merged
Merged
Conversation
oscargus
force-pushed
the
bezierdep
branch
2 times, most recently
from
May 18, 2025 13:49
48569d3 to
10f9541
Compare
oscargus
added
API: changes
QuLogic
approved these changes
May 30, 2025
dstansby
approved these changes
Jun 1, 2025
This was referenced Jun 23, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR summary
Was originally going to add a parameter description for
point_at_t, but when reading the code, it seemed to make more sense to make sure that__call__is included in the documentation and deprecatepoint_at_tinstead.PR checklist