We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Should make a decent chunk of Kite code much more readable and less error-prone.
Will need to check for everywhere we scan through segments but wouldn't use a closing segment.
The text was updated successfully, but these errors were encountered:
Not sure why I can't label this issue or edit it's description, but:
We don't want to mess up code that relies on the lack of existence of the implicit closing segment in the segments array on a closed path.
Sorry, something went wrong.
No branches or pull requests
Should make a decent chunk of Kite code much more readable and less error-prone.
Will need to check for everywhere we scan through segments but wouldn't use a closing segment.
The text was updated successfully, but these errors were encountered: