[jira] [Commented] (GROOVY-8269) Unclear/incorrect definition of default behavior for trait multiple inheritence conflicts

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (GROOVY-8269) Unclear/incorrect definition of default behavior for trait multiple inheritence conflicts

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/GROOVY-8269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16124810#comment-16124810 ]

John Wagenleitner commented on GROOVY-8269:
-------------------------------------------

Would adding a reference to the implements clause help make it more clear?

{quote}
In this case, the default behavior is that the method from the *last declared trait* in the {{implements}} clause wins.
{quote}

> Unclear/incorrect definition of default behavior for trait multiple inheritence conflicts
> -----------------------------------------------------------------------------------------
>
>                 Key: GROOVY-8269
>                 URL: https://issues.apache.org/jira/browse/GROOVY-8269
>             Project: Groovy
>          Issue Type: Documentation
>          Components: Documentation
>    Affects Versions: 2.4.12
>            Reporter: Sasha Volokh
>            Priority: Minor
>         Attachments: problem.png
>
>
> In section 2.10.1, Default conflict resolution, the text says "In this case, the default behavior is that methods from the last declared trait wins", when in fact the order they are implemented is what decides the winning method (and if this is what the wording was intending to say, then it isn't clear because the example has trait B declared after trait A as well as C implementing B after A).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)