Method cascading

In object-oriented programming, method cascading is syntax which allows multiple methods to be called on the same object. This is particularly applied in fluent interfaces.

For example, in Dart, the cascade: is equivalent to the individual calls:

Method cascading is much less common than method chaining – it is found only in a handful of object-oriented languages, while chaining is very common. A form of cascading can be implemented using chaining, but this restricts the interface; see comparison with method chaining, below.

Application
Cascading is syntactic sugar that eliminates the need to list the object repeatedly. This is particularly used in fluent interfaces, which feature many method calls on a single object.

This is particularly useful if the object is the value of a lengthy expression, as it eliminates the need to either list the expression repeatedly or use a temporary variable. For example, instead of either listing an expression repeatedly: or using a temporary variable: cascading allows the expression to be written once and used repeatedly:

Comparison with method chaining
Given a method call, after executing the call, method cascading evaluates this expression to the left object   (with its new value, if mutated), while method chaining evaluates this expression to the right object.

The following chain (in C++): is equivalent to the simple form:
 * Chaining

The following cascade (in Dart): is equivalent to the simple form:
 * Cascading

Cascading can be implemented in terms of chaining by having the methods return the target object (receiver,,  ). However, this requires that the method be implemented this way already – or the original object be wrapped in another object that does this – and that the method not return some other, potentially useful value (or nothing if that would be more appropriate, as in setters). In fluent interfaces this often means that setters return this instead of nothing.

Pascal
Within the component statement of the with statement, the components (fields) of the record variable specified by the with clause can be denoted by their field identifier only, i.e. without preceding them with the denotation of the entire record variable. The with clause effectively opens the scope containing the field identifiers of the specified record variable, so that the field identifiers may occur as variable identifiers.

Smalltalk
Method chains and cascades were both introduced in Smalltalk; most subsequent object-oriented languages have implemented chains, but few have implemented cascades. In Smalltalk the semicolon operator can be used to send different messages to the same object: Compare with separate statements, terminated with a period, also using a variable for abbreviation:

One subtlety is that the value of a method call ("message") in a cascade is still the ordinary value of the message, not the receiver. This is a problem when you do want the value of the receiver, for example when building up a complex value. This can be worked around by using the special  method that simply returns the receiver: For example, the "add an object to a collection" method returns the object that was added, not the collection. Thus to use this in a cascade in an assignment statement, the cascade must end with, otherwise the value will just be the last element added, not the collection itself:

Visual Basic
Visual Basic uses the statement to enable an arbitrary number of method calls or property accesses on the same object:

blocks in Visual Basic can be nested:

Dart
Among newer languages, Dart implements cascades, using a double-dot  "cascaded method invocation operation". Unlike Smalltalk, in Dart the value of a cascaded method invocation is the receiver (base object), not the value of the (uncascaded) method invocation, and thus there is no need for. Dart uses properties, and thus rather than using method syntax for getters and setters, it uses field value/assignment syntax , and cascades work with assignments: is equivalent to: