Skip to content
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

Dangerous BoundaryLine Optimization #859

Open
jdsika opened this issue Mar 4, 2025 · 0 comments
Open

Dangerous BoundaryLine Optimization #859

jdsika opened this issue Mar 4, 2025 · 0 comments
Assignees

Comments

@jdsika
Copy link
Contributor

jdsika commented Mar 4, 2025

Since a BoundaryPoint is part of a sequence, only the position attribute has to be set for each instance. All other values will be reused from the previous BoundaryPoint in the sequence or set to default values if there is none or it was never set.

Width and Height are of protobuffer native type "double". Therefore leaving this information away will result in the value 0 when attempting to deserialize. This is a potential source of error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants