Simon Van Accoleyen

This syntax is really not what PHP needs to be striving for. The idea is nice and SHOULD be revisited with cleaner and more modern syntax, but i'm against the proposal as it is presented right here.

With our current definition of an interface this RFC seems silly - but i really think that this could allow for faster and easier development (less files, less duplicated code...).

Just today while coding i had an example of an interface where one of the abstract functions would be the same 99% of the time. Creating a trait for a 4 liner function seems overkill - but the alternative is to duplicate the code almost everytime.

As with all other RFC with 'adding' behaviour, if you don't like it, just don't use it and left it for others :))

Creating traits for default implementation is just a pain. I want syntactic sugar

I wrote down some thoughts on this RFC on my blog. I think it's worth rethinking our current definition of what "an interface" is. Especially since many languages are interface default methods as their way of multi-inheritance.