refactor: Remove shared_ptr where possible.#775
Merged
eyal0 merged 19 commits intopcb2gcode:masterfrom Feb 28, 2026
Merged
Conversation
Collaborator
This will let us use `std::move` on it in the future. To do this, we can no longer repurpose the `cutter` as we were doing previously.
…l::vectorial_surface.
…l::make_path_finder_ring_indices.
…l::final_path_finder.
…l::make_path_finder.
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
2 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.
The code is a little too hasty to use
std::shared_ptreven where it isn't necessary. This is sloppy. We remove it everywhere except for the cases where it is used for storing a pointer to a polymorphic type in a class because that is the easiest solution for making a class that is copyable.