In object-oriented programming languages, a mixin (or mix-in) is a class that contains methods for use by other classes without having to be the parent class of those other classes. How those other classes gain access to the mixin's methods depends on the language. Mixins are sometimes described as being "included" rather than "inherited".
Mixins encourage code reuse and can be used to avoid the inheritance ambiguity that multiple inheritance can cause[1] (the "diamond problem"), or to work around lack of support for multiple inheritance in a language. A mixin can also be viewed as an interface with implemented methods. This pattern is an example of enforcing the dependency inversion principle.
Mixins first appeared in Symbolics's object-oriented Flavors system (developed by Howard Cannon), which was an approach to object-orientation used in Lisp Machine Lisp. The name was inspired by Steve's Ice Cream Parlor in Somerville, Massachusetts:[2] The owner of the ice cream shop offered a basic flavor of ice cream (vanilla, chocolate, etc.) and blended in a combination of extra items (nuts, cookies, fudge, etc.) and called the item a "mix-in", his own trademarked term at the time.[3]
Mixins are a language concept that allows a programmer to inject some code into a class. Mixin programming is a style of software development, in which units of functionality are created in a class and then mixed in with other classes.[4]
A mixin class acts as the parent class, containing the desired functionality. A subclass can then inherit or simply reuse this functionality, but not as a means of specialization. Typically, the mixin will export the desired functionality to a child class, without creating a rigid, single "is a" relationship. Here lies the important difference between the concepts of mixins and inheritance, in that the child class can still inherit all the features of the parent class, but, the semantics about the child "being a kind of" the parent need not be necessarily applied.
In Simula, classes are defined in a block in which attributes, methods and class initialization are all defined together; thus all the methods that can be invoked on a class are defined together, and the definition of the class is complete.
In Flavors, a mixin is a class from which another class can inherit slot definitions and methods. The mixin usually does not have direct instances. Since a Flavor can inherit from more than one other Flavor, it can inherit from one or more mixins. Note that the original Flavors did not use generic functions.
In New Flavors (a successor of Flavors) and CLOS, methods are organized in "generic functions". These generic functions are functions that are defined in multiple cases (methods) by class dispatch and method combinations.
CLOS and Flavors allow mixin methods to add behavior to existing methods: :before and :after daemons, whoppers and wrappers in Flavors. CLOS added :around methods and the ability to call shadowed methods via . So, for example, a stream-lock-mixin can add locking around existing methods of a stream class. In Flavors one would write a wrapper or a whopper and in CLOS one would use an :around method. Both CLOS and Flavors allow the computed reuse via method combinations. :before, :after and :around methods are a feature of the standard method combination. Other method combinations are provided.
An example is the + method combination, where the resulting values of each of the applicable methods of a generic function are arithmetically added to compute the return value. This is used, for example, with the border-mixin for graphical objects. A graphical object may have a generic width function. The border-mixin would add a border around an object and has a method computing its width. A new class bordered-button (that is both a graphical object and uses the border mixin) would compute its width by calling all applicable width methods—via the + method combination. All return values are added and create the combined width of the object.
In an OOPSLA 90 paper,[8] Gilad Bracha and William Cook reinterpret different inheritance mechanisms found in Smalltalk, Beta and CLOS as special forms of a mixin inheritance.
Other than Flavors and CLOS (a part of Common Lisp), some languages that use mixins are:
Some languages do not support mixins on the language level, but can easily mimic them by copying methods from one object to another at runtime, thereby "borrowing" the mixin's methods. This is also possible with statically typed languages, but it requires constructing a new object with the extended set of methods.
Other languages that do not support mixins can support them in a round-about way via other language constructs. For example, Visual Basic .NET and C# support the addition of extension methods on interfaces, meaning any class implementing an interface with extension methods defined will have the extension methods available as pseudo-members.
Common Lisp provides mixins in CLOS (Common Lisp Object System) similar to Flavors.
object-width is a generic function with one argument that uses the + method combination. This combination determines that all applicable methods for a generic function will be called and the results will be added.
button is a class with one slot for the button text.
There is a method for objects of class button that computes the width based on the length of the button text. + is the method qualifier for the method combination of the same name.
A border-mixin class. The naming is just a convention. There are no superclasses, and no slots.
There is a method computing the width of the border. Here it is just 4.
bordered-button is a class inheriting from both border-mixin and button.
We can now compute the width of a button. Calling object-width computes 80. The result is the result of the single applicable method: the method object-width for the class button.
We can also compute the width of a bordered-button. Calling object-width computes 84. The result is the sum of the results of the two applicable methods: the method object-width for the class button and the method object-width for the class border-mixin.
In Python, an example of the mixin concept is found in the SocketServer module,[15] which has both a UDPServer class and a TCPServer class. They act as servers for UDP and TCP socket servers, respectively. Additionally, there are two mixin classes: ForkingMixIn and ThreadingMixIn. Normally, all new connections are handled within the same process. By extending TCPServer with the ThreadingMixIn as follows:
the ThreadingMixIn class adds functionality to the TCP server such that each new connection creates a new thread. Using the same method, a ThreadingUDPServer can be created without having to duplicate the code in ThreadingMixIn. Alternatively, using the ForkingMixIn would cause the process to be forked for each new connection. Clearly, the functionality to create a new thread or fork a process is not terribly useful as a stand-alone class.
In this usage example, the mixins provide alternative underlying functionality without affecting the functionality as a socket server.
Most of the Ruby world is based around mixins via Modules. The concept of mixins is implemented in Ruby by the keyword include to which we pass the name of the module as parameter.
Example:
class Student include Comparable # The class Student inherits the Comparable module using the 'include' keyword attr_accessor :name, :score
def initialize(name, score) @name = name @score = score end
# Including the Comparable module requires the implementing class to define the <=> comparison operator # Here's the comparison operator. We compare 2 student instances based on their scores.
def <=>(other) @score <=> other.score end
# Here's the good bit - I get access to <, <=, >,>= and other methods of the Comparable Interface for free.end
s1 = Student.new("Peter", 100)s2 = Student.new("Jason", 90)
s1 > s2 #trues1 <= s2 #false
The Object-Literal and extend Approach
It is technically possible to add behavior to an object by binding functions to keys in the object. However, this lack of separation between state and behavior has drawbacks:
An extend function is used to mix the behavior in:[17]
const Halfling = function (fName, lName) ;
const mixin = ;
// An extend functionconst extend = (obj, mixin) => ;
const sam = new Halfling('Sam', 'Loawry');const frodo = new Halfling('Freeda', 'Baggs');
// Mixin the other methodsextend(Halfling.prototype, mixin);
console.log(sam.fullName); // Sam Loawryconsole.log(frodo.fullName); // Freeda Baggs
sam.rename('Samwise', 'Gamgee');frodo.rename('Frodo', 'Baggins');
console.log(sam.fullName); // Samwise Gamgeeconsole.log(frodo.fullName); // Frodo Baggins
Mixin with using Object.assign
// Creating an objectconst obj1 = ;
// Mixin 1const mix1 = ;// Mixin 2const mix2 = ;
// Adding the methods from mixins to the object using Object.assignObject.assign(obj1, mix1, mix2);
console.log(obj1.toString); // Marcus Aurelius - Rome - 121-04-26console.log(`His age is $ as of today`); // His age is 1897 as of today
The pure function and delegation based Flight-Mixin Approach
Even though the firstly described approach is mostly widespread the next one is closer to what JavaScript's language core fundamentally offers - Delegation.
Two function object based patterns already do the trick without the need of a third party's implementation of extend.
// Implementationconst EnumerableFirstLast = (function);
// Application - explicit delegation:// applying [first] and [last] enumerable behavior onto [Array]'s [prototype].EnumerableFirstLast.call(Array.prototype);
// Now you can do:const a = [1, 2, 3];a.first; // 1a.last; // 3
In the Curl web-content language, multiple inheritance is used as classes with no instances may implement methods. Common mixins include all skinnable ControlUIs inheriting from SkinnableControlUI, user interface delegate objects that require dropdown menus inheriting from StandardBaseDropdownUI and such explicitly named mixin classes as FontGraphicMixin, FontVisualMixin and NumericAxisMixin-of class. Version 7.0 added library access so that mixins do not need to be in the same package or be public abstract. Curl constructors are factories that facilitates using multiple-inheritance without explicit declaration of either interfaces or mixins.
Java 8 introduces a new feature in the form of default methods for interfaces.[18] Basically it allows a method to be defined in an interface with application in the scenario when a new method is to be added to an interface after the interface class programming setup is done. To add a new function to the interface means to implement the method at every class which uses the interface. Default methods help in this case where they can be introduced to an interface any time and have an implemented structure which is then used by the associated classes. Hence default methods add the ability to applying the mixin concept in Java.
Interfaces combined with aspect-oriented programming can also produce full-fledged mixins in languages that support such features, such as C# or Java. Additionally, through the use of the marker interface pattern, generic programming, and extension methods, C# 3.0 has the ability to mimic mixins. With Dart 2.7 and C# 3.0 came the introduction of extension methods which can be applied, not only to classes, but also to interfaces. Extension Methods provide additional functionality on an existing class without modifying the class. It then becomes possible to create a static helper class for specific functionality that defines the extension methods. Because the classes implement the interface (even if the actual interface doesn’t contain any methods or properties to implement) it will pick up all the extension methods also.[19] [20] [21] C# 8.0 adds the feature of default interface methods.[22] [23]
ECMAScript (in most cases implemented as JavaScript) does not need to mimic object composition by step-wise copying fields from one object to another. It natively[24] supports Trait and mixin[25] [26] based object composition via function objects that implement additional behavior and then are delegated via call or apply to objects that are in need of such new functionality.
Scala has a rich type system and Traits are a part of it which helps implement mixin behaviour. As their name reveals, Traits are usually used to represent a distinct feature or aspect that is normally orthogonal to the responsibility of a concrete type or at least of a certain instance.[27] For example, the ability to sing is modeled as such an orthogonal feature: it could be applied to Birds, Persons, etc.
class Bird extends Singer
Here, Bird has mixed in all methods of the trait into its own definition as if class Bird had defined method sing on its own.
As extends is also used to inherit from a super class, in case of a trait extends is used if no super class is inherited and only for mixin in the first trait. All following traits are mixed in using keyword with.
Scala allows mixing in a trait (creating an anonymous type) when creating a new instance of a class. In the case of a Person class instance, not all instances can sing. This feature comes use then:
val singingPerson = new Person with SingersingingPerson.sing
Rust makes extensive use of mixins via traits. Traits, like in Scala, allow users to implement behaviours for a defined type. They are also used for generics and dynamic dispatch, allowing types implementing a trait to be used interchangeably statically or dynamically at runtime.[28]
struct Dog;
impl Speak for Dog
struct Robot;
impl Speak for Robot
Mixin can be achieved in Swift by using a language feature called Default implementation in Protocol Extension.
extension ErrorDisplayable
struct NetworkManager : ErrorDisplayable