[
https://issues.apache.org/jira/browse/JENA-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15474485#comment-15474485
]
ASF GitHub Bot commented on JENA-1231:
--------------------------------------
Github user afs commented on the issue:
https://github.com/apache/jena/pull/168
The second commit,
https://github.com/apache/jena/pull/168/commits/1d6a4758de9305d9fe25e08b7594bbda8bd36a83,
uses execute/calculate style naming.
For discussion (the PR would be tidied up before merging into Jena).
> Update "executeInTransaction" to Java8 style (Model, TransactionHandler).
> -------------------------------------------------------------------------
>
> Key: JENA-1231
> URL: https://issues.apache.org/jira/browse/JENA-1231
> Project: Apache Jena
> Issue Type: Bug
> Affects Versions: Jena 3.1.0
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Minor
>
> The proposal is to deprecate {{executeInTransaction}}, which returns "Object"
> and have operations:
> {noformat}
> <T> T executeRtn( Supplier<T> action ) ;
> {noformat}
> and the non-result version:
> {noformat}
> void execute( Runnable action );
> {noformat}
> It helps in the IDE to have different names because they both start
> "{{()\->...}}". In my experience (Eclipse) completion and error messages are
> not good when there is the same name and ambiguity over the inferred type.
> Using the {{()->methodresultsvalue()}} form is ambiguous.
> For model, call them {{executeInTxnRtn}} and {{executeInTxn}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
