Content deleted Content added
No edit summary |
|||
(13 intermediate revisions by 10 users not shown) | |||
Line 1:
{{Short description|Using one interface or symbol with regards to multiple different types}}
{{
{{Polymorphism}}
In [[programming language theory]] and [[type theory]], '''polymorphism''' is the
In [[object-oriented programming]], polymorphism is the provision of one [[Interface (object-oriented programming)|interface]] to entities of different [[data type]]s.<ref>{{cite web |
▲{{cite web | url=http://www.stroustrup.com/glossary.html#Gpolymorphism | author=Bjarne Stroustrup | title=Bjarne Stroustrup's C++ Glossary | date=February 19, 2007 | quote=polymorphism – providing a single interface to entities of different types.}}</ref> The concept is borrowed from a principle in [[biology]] where an organism or species can have many different forms or stages.<ref name="Moved">{{cite web | title=Polymorphism |work=The Java™ Tutorials: Learning the Java Language: Interfaces and Inheritance |publisher=Oracle | url=https://docs.oracle.com/javase/tutorial/java/IandI/polymorphism.html | access-date=2021-09-08}}</ref>
The most commonly recognized major forms of polymorphism are:
* ''[[Ad hoc polymorphism]]'': defines a common interface for an arbitrary set of individually specified types.
* ''[[Parametric polymorphism]]'': not specifying concrete types and instead use abstract symbols that can substitute for any type.
* ''[[Subtyping]]'' (also called ''subtype polymorphism'' or ''inclusion polymorphism''): when a name denotes instances of many different classes related by some common superclass.<ref name="gbooch">{{cite book |last1=Conallen |first1=J. |last2=Engle |first2=M. |last3=Houston |first3=K. |last4=Maksimchuk |first4=R. |last5=Young |first5=B. |last6=Booch |first6=G. |author6-link=Grady Booch |date=2007 |title=Object-Oriented Analysis and Design with Applications |publisher=Pearson Education |edition=3rd
==History==
Interest in polymorphic [[type system]]s developed significantly in the 1990s, with practical implementations beginning to appear by the end of the decade.
In a 1985 paper, [[Peter Wegner (computer scientist)|Peter Wegner]] and [[Luca Cardelli]] introduced the term ''inclusion polymorphism'' to model subtypes and [[Inheritance (object-oriented programming)|inheritance]],<ref name="Luca"/> citing [[Simula]] as the first programming language to implement it.
==Forms==
===Ad hoc polymorphism===
{{
[[Christopher Strachey]] chose the term ''ad hoc polymorphism'' to refer to polymorphic functions that can be applied to arguments of different types, but that behave differently depending on the type of the argument to which they are applied (also known as [[function overloading]] or [[operator overloading]]).<ref name=Strachey00/> The term "[[ad hoc]]" in this context is not
<syntaxhighlight lang="
class AdHocPolymorphic {
public String add(int x, int y) {
return "Sum: " + (x + y);
}
public String add(String name) {
return "Added " + name;
}
}
public class
public static void main(String[] args) {
AdHocPolymorphic poly = new AdHocPolymorphic();
System.out.println(
System.out.println(
}
}
Line 45 ⟶ 44:
In [[dynamically typed]] languages the situation can be more complex as the correct function that needs to be invoked might only be determinable at run time.
[[Implicit type conversion]] has also been defined as a form of polymorphism, referred to as "coercion polymorphism".<ref name="Luca"/><ref name="Tucker2004">{{cite book |
===Parametric polymorphism===
{{
''Parametric polymorphism'' allows a function or a data type to be written generically, so that it can handle values ''uniformly'' without depending on their type.<ref name="bjpierce">{{cite book |
The concept of parametric polymorphism applies to both [[data type]]s and [[
Parametric polymorphism is ubiquitous in functional programming, where it is often simply referred to as "polymorphism". The
<syntaxhighlight lang="Haskell">
Line 67 ⟶ 66:
</syntaxhighlight>
Parametric polymorphism is also available in several object-oriented languages. For instance, [[Template (C++)|templates]] in [[C++]] and [[D (programming language)|D]], or under the name [[Generics in Java|generics]] in [[C Sharp (programming language)|C#]], [[Delphi (software)|Delphi]], Java, and [[Go (programming language)|Go]]:
<syntaxhighlight lang="CSharp">
Line 87 ⟶ 86:
===Subtyping===
{{
Some languages employ the idea of ''subtyping'' (also called ''subtype polymorphism'' or ''inclusion polymorphism'') to restrict the range of types that can be used in a particular case of polymorphism. In these languages, subtyping allows a function to be written to take an object of a certain type ''T'', but also work correctly, if passed an object that belongs to a type ''S'' that is a subtype of ''T'' (according to the [[Liskov substitution principle]]). This type relation is sometimes written {{nowrap|''S''
In the following Java example
<syntaxhighlight lang="java">
Line 110 ⟶ 109:
static void letsHear(final Pet pet) {
System.out.println(pet.speak());
}
Line 121 ⟶ 120:
[[File:UML class pet.svg]]
In another example, if ''Number'', ''Rational'', and ''Integer'' are types such that {{nowrap|''Number''
[[Object-oriented programming language]]s offer subtype polymorphism using ''[[Subclass (computer science)|subclass]]ing'' (also known as ''[[inheritance in object-oriented programming|inheritance]]''). In typical implementations, each class contains what is called a ''[[virtual table]]'' (shortly called ''vtable'') — a table of functions that implement the polymorphic part of the class interface—and each object contains a pointer to the vtable of its class, which is then consulted whenever a polymorphic method is called. This mechanism is an example of:
Line 131 ⟶ 130:
===Row polymorphism===
{{
{{see also|Duck typing}}
Row polymorphism<ref>
{{cite conference
|
|
|
|
|
|
|
</ref> is a similar, but distinct concept from subtyping. It deals with [[Structural type system|structural types]]. It allows the usage of all values whose types have certain properties, without losing the remaining type information.
===Polytypism===
{{
A related concept is ''polytypism'' (or ''data type genericity''). A polytypic function is more general than polymorphic, and in such a function, "though one can provide fixed ad hoc cases for specific data types, an ad hoc combinator is absent".<ref>{{cite book |first1=Ralf |last1=Lämmel |first2=Joost |last2=Visser |chapter=Typed Combinators for Generic Traversal |title=Practical Aspects of Declarative Languages: 4th International Symposium |publisher=Springer |date=2002 |isbn=354043092X |pages=137–154, See p. 153 |citeseerx=10.1.1.18.5727 |url=}}</ref>
===Rank polymorphism===
Rank polymorphism is one of the defining features of the [[
==Implementation aspects==
===Static and dynamic polymorphism===
{{
Polymorphism can be distinguished by when the implementation is selected: statically (at compile time) or dynamically (at run time, typically via a [[virtual function]]). This is known respectively as ''[[static dispatch]]'' and ''[[dynamic dispatch]],'' and the corresponding forms of polymorphism are accordingly called ''static polymorphism'' and ''dynamic polymorphism''.
Static polymorphism executes faster, because there is no dynamic dispatch overhead, but requires additional compiler support. Further, static polymorphism allows greater static analysis by compilers (notably for optimization), source code analysis tools, and human readers (programmers). Dynamic polymorphism is more flexible but slower—for example, dynamic polymorphism allows [[Duck typing|duck typing]], and a dynamically linked library may operate on objects without knowing their full type.
Static polymorphism typically occurs in ad hoc polymorphism and parametric polymorphism, whereas dynamic polymorphism is usual for subtype polymorphism. However, it is possible to achieve static polymorphism with subtyping through more sophisticated use of [[template metaprogramming]], namely the [[curiously recurring template pattern]].
When polymorphism is exposed via a [[Library (computing)|library]], static polymorphism becomes impossible for [[dynamic libraries]] as there is no way of knowing what types the parameters are when the [[shared object]] is built. While languages like C++ and Rust use [[monomorphization|monomorphized]] templates, the [[Swift programming language]] makes extensive use of dynamic dispatch to build the [[application binary interface]] for these libraries by default. As a result, more code can be shared for a reduced system size at the cost of runtime overhead.<ref>{{cite web |last1=Beingessner |first1=Alexis |title=How Swift Achieved Dynamic Linking Where Rust Couldn't |url=https://gankra.github.io/blah/swift-abi/
==See also==
Line 170 ⟶ 169:
==References==
{{
==External links==
Line 182 ⟶ 181:
{{DEFAULTSORT:Polymorphism}}
[[Category:Polymorphism (computer science)| ]]
[[Category:Articles with example C Sharp code]]▼
[[Category:Articles with example Haskell code]]▼
[[Category:Articles with example Java code]]▼
[[Category:Articles with example Pascal code]]▼
[[Category:Data types]]
[[Category:Functional programming]]
Line 192 ⟶ 187:
[[Category:Type theory]]
[[Category:Generic programming]]
[[Category:Programming language comparisons]]
<!-- Hidden categories below -->
▲[[Category:Articles with example C Sharp code]]
▲[[Category:Articles with example Haskell code]]
▲[[Category:Articles with example Java code]]
▲[[Category:Articles with example Pascal code]]
|