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

Extract a common "values" area type #1

Closed
io7m opened this Issue Mar 8, 2017 · 0 comments

Comments

Projects
None yet
1 participant
@io7m
Owner

io7m commented Mar 8, 2017

APIs such as jcanephora need to be able to work with area types regardless of whether the concrete implementation is a PArea or plain Area. In other words, right now an API such as jcanephora will end up forcing the user to use either PAreas or Areas even though the types are functionally identical.

@io7m io7m added the enhancement label Mar 8, 2017

@io7m io7m self-assigned this Mar 8, 2017

@io7m io7m changed the title from Extra a common "values" area type to Extract a common "values" area type Mar 8, 2017

@io7m io7m closed this in cac8754 Mar 8, 2017

io7m added a commit that referenced this issue Mar 10, 2017

Merge branch 'release/0.0.3'
Release: jregions 0.0.3
Code new: Add common "value" interfaces. (tickets: #1)
Code new: Add missing float and BigDecimal generators and tests. (tickets: #4)
Code new: Add type conversion methods. (tickets: #3)
Code new: Allow areas to be treated as area sizes. (tickets: #5)
Code new: Add methods to return sizes from areas. (tickets: #2)

io7m added a commit that referenced this issue Mar 10, 2017

Merge tag 'jregions-0.0.3' into develop
Release: jregions 0.0.3

Code new: Add common "value" interfaces. (tickets: #1)
Code new: Add missing float and BigDecimal generators and tests. (tickets: #4)
Code new: Add type conversion methods. (tickets: #3)
Code new: Allow areas to be treated as area sizes. (tickets: #5)
Code new: Add methods to return sizes from areas. (tickets: #2)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment