Skip to content

Use List instead of Iterable as returntype of ModuleInfo methods. #217

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

Merged
merged 1 commit into from
Jan 18, 2016
Merged

Use List instead of Iterable as returntype of ModuleInfo methods. #217

merged 1 commit into from
Jan 18, 2016

Conversation

gab1one
Copy link
Contributor

@gab1one gab1one commented Jan 18, 2016

that return a list of ModuleItems.

inputs() and outputs() used to return Iterable<ModuleItem<?>>this made random access on a Module's inputs and outputs painful. This restriction is not needed as the implementations of ModuleInfo already return a List. This change breaks compatibility with custom implementations of ModuleInfo, but not with any calls to the changed methods, as List is still Iterable.

…returning list of ModuleItems.

``inputs()`` and ``outputs()`` used to return Iterable<ModuleItem<?>> this made random access on a Module's in and outputs painful. This restriction is not needed as the implementations of ModuleInfo already return a List.
ctrueden added a commit that referenced this pull request Jan 18, 2016
Use List instead of Iterable as returntype of ModuleInfo methods.
@ctrueden ctrueden merged commit 2d3ff66 into scijava:master Jan 18, 2016
@ctrueden
Copy link
Member

Thanks, this is long (looooooong) overdue! 😹

@ctrueden
Copy link
Member

ctrueden commented Feb 5, 2016

Reverted in edfc7c5 😭

@gab1one gab1one deleted the iterable-to-list branch January 4, 2017 17:29
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.

3 participants