You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@groovy.apache.org by "Paul King (JIRA)" <ji...@apache.org> on 2017/07/27 02:15:00 UTC

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

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

Paul King commented on GROOVY-8269:
-----------------------------------

I haven't had time to check yet but if you can include which Groovy version(s) you are using, that would be great. Thanks.

> 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
>            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)