Trait (computer programming)

This article may be too technical for most readers to understand. Please help improve it to make it understandable to non-experts, without removing the technical details. (March 2012) (Learn how and when to remove this message)

This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Trait" computer programming – news · newspapers · books · scholar · JSTOR (November 2022) (Learn how and when to remove this message)

In computer programming, a trait is a language concept that represents a set of methods that can be used to extend the functionality of a class.^[1][2]

In object-oriented programming, behavior is sometimes shared between classes which are not related to each other. For example, many unrelated classes may have methods to serialize objects to JSON. Historically, there have been several approaches to solve this without duplicating the code in every class needing the behavior. Other approaches include multiple inheritance and mixins, but these have drawbacks: the behavior of the code may unexpectedly change if the order in which the mixins are applied is altered, or if new methods are added to the parent classes or mixins.

Traits solve these problems by allowing classes to use the trait and get the desired behavior. If a class uses more than one trait, the order in which the traits are used does not matter. The methods provided by the traits have direct access to the data of the class.

Traits combine aspects of protocols (interfaces) and mixins. Like an interface, a trait defines one or more method signatures, of which implementing classes must provide implementations. Like a mixin, a trait provides additional behavior for the implementing class.

In case of a naming collision between methods provided by different traits, the programmer must explicitly disambiguate which one of those methods will be used in the class; thus manually solving the diamond problem of multiple inheritance. This is different from other composition methods in object-oriented programming, where conflicting names are automatically resolved by scoping rules.

Operations which can be performed with traits include:^[3][4]

• symmetric sum: an operation that merges two disjoint traits to create a new trait
• override (or asymmetric sum): an operation that forms a new trait by adding methods to an existing trait, possibly overriding some of its methods
• alias: an operation that creates a new trait by adding a new name for an existing method
• exclusion: an operation that forms a new trait by removing a method from an existing trait. (Combining this with the alias operation yields a shallow rename operation).

If a method is excluded from a trait, that method must be provided by the class that consumes the trait, or by a parent class of that class. This is because the methods provided by the trait might call the excluded method.

Trait composition is commutative (i.e. given traits A and B, A + B is equivalent to B + A) and associative (i.e. given traits A, B, and C, (A + B) + C is equivalent to A + (B + C)).^[1]

While traits offer significant advantages over many alternatives, they do have their own limitations.

If a trait requires the consuming class to provide certain methods, the trait cannot know if those methods are semantically equivalent to the trait's needs. For some dynamic languages, such as Perl, the required method can only be identified by a method name, not a full method signature, making it harder to guarantee that the required method is appropriate.

If a method is excluded from a trait, that method becomes a 'required' method for the trait because the trait's other methods might call it.

Traits originate in the programming language Self^[5] and are supported by these programming languages:

• AmbientTalk: Combines the properties of Self traits (object-based multiple inheritance) and Smalltalk's Squeak traits (requiring explicit composition of traits by the programmer). It builds on the research on stateful and freezable traits to enable state within traits, which was not allowed in the first definitions.^[6]
• C#: Since version 8.0, C# supports default interface methods,^[7] which have some properties of traits.^[8]
• C++: Used in Standard Template Library and the C++ Standard Library to support generic container classes^[9][10] and in the Boost TypeTraits library.^[11]
• Curl: Abstract classes as mixins permit method implementations and thus constitute traits by another name.^{[citation needed]}
• Fortress^[12]
• Groovy: Since version 2.3^[13]
• Haskell: Traits are named Type classes.
• Haxe: Since version 2.4.0.^[14] Called Static Extension^[15] in the manual, it uses using keyword
• Java: Since version 8, Java supports default methods,^[16] which have some properties of traits.^{[17][18][19][20]}
• JavaScript: Traits can be implemented via functions and delegations^[21] or through libraries that provide traits.^[22][23][24]
• Julia: Several packages implement traits, e.g.,^[25]
• Kotlin: Traits have been called interfaces^[26] since M12.^[27]
• Lasso^[28]
• Mojo: Since version 0.6.0^[29]
• OCaml: Traits can be implemented using a variety of language features: module and module type inclusion, functors and functor types, class and class type inheritance, et cetera.
• Perl: Named roles, they are implemented in Perl libraries such as Moose, Role::Tiny and Role::Basic. Roles are part of the sister language Raku. ^[30] With the acceptance of the Corinna OOP Proposal^[31] Perl will have roles native to the language as part of a modern OOP system.
• PHP: Since version 5.4,^[32][33] PHP allows users to specify templates that provide the ability to "inherit" from more than one (trait-)class, as a pseudo multiple inheritance.
• Python: Via a third-party library,^[34][35] or via higher-order mixin classes^[36]
• Racket: Supports traits as a library and uses macros, structures, and first-class classes to implement them.^[37]
• Ruby: Module mixins can be used to implement traits.^[38]
• Rust^[39]
• Scala^[40][41] trait is builtin supported with the key word trait.
• Smalltalk: Traits are implemented in two dialects of Smalltalk, Squeak^[1] and Pharo.^[42]
• Swift: Traits can be implemented with protocol extensions.^[43]

On C# 8.0, it is possible to define an implementation as a member of an interface.

using System;

namespace CSharp8NewFeatures;

interface ILogger
{
    // Traditional interface methods
    void Log(string message);
    void LogError(Exception exception);

    // Default interface method
    void LogWarning(string message)
    {
        Console.WriteLine(message);
    }        
}

class Logger : ILogger
{
    public void Log(string message)
    {
        Console.WriteLine(message);
    }

    public void LogError(Exception exception)
    {
        Console.WriteLine(exception.ToString());
    }
}

public class Program
{
    static void Main(string[] args)
    {
        ILogger logger = new Logger();

        logger.LogWarning("Some warning message");
    }
}

This example uses a trait to enhance other classes:

// The template
trait TSingleton
{
    private static $_instance = null;

    private function __construct() {} // Must have private default constructor and be aware not to open it in the class

    public static function getInstance()
    {
        if (null === self::$_instance) {
            self::$_instance = new self();
        }

        return self::$_instance;
    }
}

class FrontController
{
    use TSingleton;
}

// Can also be used in already extended classes
class WebSite extends SomeClass
{
    use TSingleton;
}

This allows simulating aspects of multiple inheritance:

trait TBounding
{
    public $x, $y, $width, $height;
}

trait TMoveable
{
    public function moveTo($x, $y)
    {
        // …
    }
}

trait TResizeable
{
    public function resize($newWidth, $newHeight)
    {
        // …
    }
}

class Rectangle
{
    use TBounding, TMoveable, TResizeable;

    public function fillColor($color)
    {
        // …
    }
}

A trait in Rust declares a set of methods that a type must implement.^[44] Rust compilers require traits to be explicated, which ensures the safety of generics in Rust.

// type T must have the "Ord" trait
// so that ">" and "<" operations can be done
fn max<T: Ord>(a: &[T]) -> Option<&T> {
    let mut result = a.first()?;
    for n in a {
        if *n > *result {
            result = &n;
        }
    }
    Some(result)
}

To simplify tedious and repeated implementation of traits like Debug and Ord, the derive macro can be used to request compilers to generate certain implementations automatically.^[45] Derivable traits include: Clone, Copy, Debug, Default, PartialEq, Eq, PartialOrd, Ord and Hash.

• Extension method
• Interface (object-oriented programming)
• Parametric polymorphism
• UFCS

• "Traits: Composable Units of Behavior". Software Composition Group. University of Bern.