trait support

[peachpiecompiler]

trait support

[jakubmisek]

@Xon yes it works. Inside the trait method, members will be accessed dynamically.

Just my personal note: it is not a good practice to call something that is not there in design time. Compose class with instances of services instead of traits, or define abstract methods in the trait. Otherwise bad trait pushes developers to create an unmaintainable piece code.

[Xon]

It wouldn't be so bad if you could restrict a trait to being used to class implements a particular interface/abstract class.

But the php traits where added back int the php 5.4 days, and don't appear to have been touched spec-wise in the php 7.x language updates.

[jakubmisek]

Closing as implemented in order to run our test cases and PHP examples successfully.

[ztl8702]

+1 for this. Was trying to compile Drupal 8 using Peachpie and then realised that Drupal 8 uses PHP trait extensively.

[hadi77ir]

Isn't it possible to implement traits using interfaces?

[jakubmisek]

@hadi77ir traits have implementations and fields and can extend other classes. Even tho CLR allows interfaces with implementations I think it wouldn't be a good practice. Also this wouldn't allow trait members aliasing.

[jakubmisek]

preview of trait support implemented in 81bee0e

[Xon]

@jakubmisek php implements traits as basically copy & pasting a trait into a class's namespace. This means constants, fields and methods of the hosting class can be called by any trait method as if it was part of the trait.

Would the generated separate class implementation allow this?