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

Add new geo-traits crate #1019

Closed
wants to merge 17 commits into from
Closed

Add new geo-traits crate #1019

wants to merge 17 commits into from

Conversation

frewsxcv
Copy link
Member

  • I agree to follow the project's code of conduct.
  • I added an entry to 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.

kylebarron and others added 15 commits February 8, 2023 23:07
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 https://github.com/georust/geo/discussions/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]>
@RobWalt
Copy link
Contributor

RobWalt commented Jun 30, 2023

Just a comment: I think the name of the crate is a bit confusing. Since geo relies on the num crate quiet heavily I thought the new geo-traits crate was similar to the num-traits crate which separates all the traits one can find in num nicely so we don't have to pull in all of num everywhere.

However, it seems that geo-traits implements entirely new traits instead.

I was just looking for a lightweight way to get the HasKernel trait which is required for a data type I'm defining in a separate crate for use everywhere else

kylebarron and others added 2 commits November 27, 2023 01:17
* Merge branch 'main'

* Remove unneeded trait lifetime in geo-traits

* bump MSRV for geo-traits CI

---------

Co-authored-by: Michael Kirk <[email protected]>
@kylebarron kylebarron mentioned this pull request Feb 26, 2024
2 tasks
@frewsxcv
Copy link
Member Author

Closing in favor of #1157

@frewsxcv frewsxcv closed this Mar 16, 2024
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

Successfully merging this pull request may close these issues.

None yet

3 participants