You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Eric Milles (Jira)" <ji...@apache.org> on 2022/09/06 00:30:00 UTC
[jira] [Updated] (GROOVY-10714) STC can't distinguish overloads
[ https://issues.apache.org/jira/browse/GROOVY-10714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Milles updated GROOVY-10714:
---------------------------------
Fix Version/s: 3.0.13
> STC can't distinguish overloads
> -------------------------------
>
> Key: GROOVY-10714
> URL: https://issues.apache.org/jira/browse/GROOVY-10714
> Project: Groovy
> Issue Type: Bug
> Components: Static compilation
> Affects Versions: 4.0.4
> Reporter: Christopher Smith
> Assignee: Eric Milles
> Priority: Minor
> Fix For: 4.0.5, 3.0.13
>
>
> This appears to be similar to GROOVY-9881, but it's specifically in the method-overload procedure. Given a functional value type with two method overloads:
> {code}
> interface Try<T> {
> Try<T> andThenTry(Consumer<? super T>)
> Try<T> andThenTry(Runnable)
> }
> {code}
> When this code is invoked from static code, the STC errors out on an ambiguous method reference even if the method type isn't:
> {code}
> // AWS SDK 2 DynamoDbTable
> class DynamoDbTable {
> void putItem(PutItemRequest<T>)
> void putItem(Consumer<PutItemRequest.Builder<T>)
> void putItem(T)
> }
> @CompileStatic
> class MyServiceClass {
> void doThing() {
> Try.success(putItemRequest())
> .andThenTry(table::putItem) // T for Try<T> is PutItemRequest<I>
> }
> }
> {code}
> produces
> {code}
> [Static type checking] - Reference to method is ambiguous. Cannot choose between [Try<T> Try#andThenTry(Consumer<? super T>), Try<T> Try#andThenTry(Runnable)]
> {code}
> I think this may have something to do with the relaxed SAM matching that is used to bridge ambiguous closure syntax, but when a plain method reference is used, there's no ambiguity available.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)