Extract a common "values" area type #1
Assignees
Labels
Comments
io7m
changed the title
io7m
added a commit
that referenced
this issue
Mar 10, 2017
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
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
APIs such as
jcanephoraneed to be able to work with area types regardless of whether the concrete implementation is aPAreaor plainArea. In other words, right now an API such asjcanephorawill end up forcing the user to use eitherPAreasorAreaseven though the types are functionally identical.The text was updated successfully, but these errors were encountered: