[ https://issues.apache.org/jira/browse/ZEST-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15681328#comment-15681328 ]
Paul Merlin commented on ZEST-120: ---------------------------------- Added unit test demonstrating actual behaviour in 64d6d81ce945434d908e1614ce05bc2c935e089f That is, bootstrap fails because the composites do not implement the offending methods. Some aspects of default methods: - they are part of an interface contract - they can be overridden by child interfaces - they can be implemented by child classes / mixins I think we should have first class support for default methods, controlling their invocation stack. > Figure out the semantics for Default Methods in interfaces > ---------------------------------------------------------- > > Key: ZEST-120 > URL: https://issues.apache.org/jira/browse/ZEST-120 > Project: Zest > Issue Type: Bug > Reporter: Niclas Hedhman > > The introduction of default methods in Java 8 has impact on Zest. > * What semantics should we assign to it? > * How does the compiler deal with it? > * Do we need to intercept the call, to ensure the invocation stack is > called? -- This message was sent by Atlassian JIRA (v6.3.4#6332)