Abstract type

In programming languages, an abstract type is a type in a nominative type system that cannot be instantiated directly. Abstract types are also known as existential types.^[1] An abstract type may provide no implementation, or an incomplete implementation. Often, abstract types will have one or more implementations provided separately, for example, in the form of concrete subclasses that can be instantiated. It may include abstract methods or abstract properties^[2] that are shared by its subtypes.

The object oriented form of abstract types are known as abstract base classes or simply abstract classes. In some languages, abstract types with no implementation are known as protocols, interfaces, signatures, class types. Other names for language features that are (or may be) used to implement abstract types include traits, mixins, flavors, roles, or type classes.

A type that is not abstract is called a concrete type (or concrete class).

Signifying abstract types

Abstract classes can be created, signified, or simulated in several ways:

• By use of the explicit keyword abstract in the class definition, as in Java, D or C#.
• By including, in the class definition, one or more abstract methods (called pure virtual functions in C++), which the class is declared to accept as part of its protocol, but for which no implementation is provided.
• By inheriting from an abstract type, and not overriding all missing features necessary to complete the class definition.
• In many dynamically typed languages such as Smalltalk, any class that sends a particular method to this, but doesn't implement that method, can be considered abstract. (However, in many such languages, like Objective-C, the error is not detected until the class is used, and the message returns results in an exception error message such as "Does not recognize selector: xxx" as - [NSObject doesNotRecognizeSelector:(SEL)selector] is invoked upon detection of an unimplemented method).

Example (Java)

//By default, all methods in all classes are concrete, unless the abstract keyword is used.
abstract class Demo {
    // An abstract class may include abstract methods, which have no implementation.
    abstract public int sum(int x, int y);

    // An abstract class may also include concrete methods.
    public int product(int x, int y) { return x*y; }
}

//By default, all methods in all interfaces are abstract, unless the default keyword is used.
interface DemoInterface {
    [abstract] int getLength(); //Abstract can be used here, though is completely useless
    
    //The default keyword can be used in this context to specify a concrete method in an interface
    default int product(int x, int y) {
        return x * y;
    }
}

Use of abstract types

Abstract types are an important feature in statically typed OOP languages. Many dynamically typed languages have no equivalent feature (although the use of duck typing makes abstract types unnecessary); however traits are found in some modern dynamically-typed languages.

Some authors argue that classes should be leaf classes (have no subtypes), or else be abstract.^[3][4]

Abstract types are useful in that they can be used to define and enforce a protocol; a set of operations that all objects implementing the protocol must support.

See also

• Class

References

Further reading

• Head First Java. O'Reilly Media. 2003. p. 688. ISBN 0-596-00920-8. 
• Core Java: An Integrated Approach by R. Nageswara Rao

External links

• "Abstract or Skeletal Interfaces Explained"
• Types and Programming Languages by Benjamin Pierce (MIT Press 2002)
• Abstract type at Rosetta Code