An interface promises nothing about an action! The source of the confusion is that in most languages, if you have an interface type that defines a set of methods, the class that implements it "repeats" the same methods (but provides definition), so the interface looks like a skeleton or an outline of the class.
The first word in the interface value points at what I call an interface table or itable (pronounced i-table; in the runtime sources, the C implementation name is Itab). The itable begins with some metadata about the types involved and then becomes a list of function pointers.
42 The interface keyword indicates that you are declaring a traditional interface class in Java. The @interface keyword is used to declare a new annotation type. See docs.oracle tutorial on annotations for a description of the syntax. See the JLS if you really want to get into the details of what @interface means.
An interface is a good example of loose coupling (dynamic polymorphism/dynamic binding) An interface implements polymorphism and abstraction.It tells what to do but how to do is defined by the implementing class.
OP asked for interface, I assume it is extended with other properties and methods, you cannot do that with a type and also type is more limited than an interfaces in terms of general usability
An interface in java is a special type of Abstract class, the Interface provided the 100% Abstraction but since the java introduce new features in java 8 the meaning of whole Interface is change.
An Interface is more of a high level architectural tool (which becomes clearer if you start to grasp design patterns) - an Abstract has a foot in both camps and can perform some of the dirty work too. Why use one over the other? The former allows for a more concrete definition of descendants - the latter allows for greater polymorphism.
Interface inheritance is an excellent tool, though you should only use it when interface B is truly substitutable for interface A, not just to aggregate loosely-related behaviors. It's difficult to tell whether it is appropriate for your specific case, but there's nothing wrong using the practice in principle. You see it in the first-rate APIs all the time. To pick just one common example ...
Is there a way to change the type of interface property defined in a *.d.ts in typescript? for example: An interface in x.d.ts is defined as interface A { property: number; } I want to change...
