googlefonts / googlefonts/glyphsLib

Why is there a GSPath.clone() and not GSPath.copy()

Open
#913 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
201
Forks
56
Avg merge
17m
Merged PRs (30d)
1

Description

Can’t we just use `.copy()` (that would copy attributes and such, too) shouldn’t be much slower? (@simoncozens)

Contributor guide

Open the contributing guide

Research direction

Start by locating the GSPath.clone() implementation and any existing GSPath.copy() behavior or call sites. Compare whether copying attributes preserves the same behavior and assess the stated performance concern. Done means establishing whether clone can be replaced by copy and documenting or implementing the agreed change.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.