-
Notifications
You must be signed in to change notification settings - Fork 200
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
Add new geo-traits
crate
#1019
Add new geo-traits
crate
#1019
Conversation
1011: Initial geo-traits implementation r=frewsxcv a=kylebarron - [x] I agree to follow the project's [code of conduct](https://github.com/georust/geo/blob/main/CODE_OF_CONDUCT.md). - [ ] I added an entry to `CHANGES.md` if knowledge of this change could be valuable to users. --- As discussed on the discord, in #838, and originally in #67, this is an initial bare-bones implementation of geometry access traits for discussion. As `@frewsxcv` suggested, for now this is a separate crate in the workspace to let us iterate on some ideas. ### Future work #### Minimize cloning in the geo-types implementation I got lost in lifetime errors so to get things to compile I added cloning to the geo-types implementations. I.e. for `MultiPoint` each point is cloned when accessed. Co-authored-by: Kyle Barron <[email protected]>
Just a comment: I think the name of the crate is a bit confusing. Since However, it seems that I was just looking for a lightweight way to get the |
* Merge branch 'main' * Remove unneeded trait lifetime in geo-traits * bump MSRV for geo-traits CI --------- Co-authored-by: Michael Kirk <[email protected]>
Closing in favor of #1157 |
CHANGES.md
if knowledge of this change could be valuable to users.See #1011. We can use this draft pull request to view the changes from the work-in-progress
traits
branch.