[
https://issues.apache.org/jira/browse/GEOMETRY-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527276#comment-17527276
]
Matt Juntunen commented on GEOMETRY-144:
----------------------------------------
Having thought on this some more, I believe the best way to go here would be to
just implement a single algorithm and hide the details from the user, similar
to how the JDK's {{Arrays.sort}} uses TimSort internally. If this ends up being
insufficient, then we could add additional algorithms through an enum for use
in special cases, while still retaining the API for the general-purpose use
case. This seems cleaner to me than adding several algorithm options at first
and then trying to revert to a single-algorithm API if there are not any
compelling use cases for the different algorithms (which I suspect will end up
being the case).
> Review API in "hull" module
> ---------------------------
>
> Key: GEOMETRY-144
> URL: https://issues.apache.org/jira/browse/GEOMETRY-144
> Project: Commons Geometry
> Issue Type: Task
> Reporter: Gilles Sadowski
> Assignee: Gilles Sadowski
> Priority: Minor
> Fix For: 1.1
>
>
> Review codes in the
> [{{commons-geometry-hull}}|https://gitbox.apache.org/repos/asf?p=commons-geometry.git;a=tree;f=commons-geometry-hull;hb=HEAD]
> module.
> (x) Minimize the public API
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
