You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the biggest performance costs in topojson.feature (and topojson.mesh) is calling array.slice on every point. There are times when this is needed, but in many cases it would be perfectly reasonable to modify the coordinates in-place when applying the transform, and to avoid the copy when creating a feature or mesh. We should design an appropriate API to enable this faster path.
One of the biggest performance costs in topojson.feature (and topojson.mesh) is calling array.slice on every point. There are times when this is needed, but in many cases it would be perfectly reasonable to modify the coordinates in-place when applying the transform, and to avoid the copy when creating a feature or mesh. We should design an appropriate API to enable this faster path.
Moved from topojson/topojson#215.
The text was updated successfully, but these errors were encountered: