Uniform function call syntax

Uniform function call syntax (UFCS) or uniform call syntax (UCS) is a programming language feature in D, Nim, Koka, Effekt, , Lean , and other programming languages, that allows any function to be called using the syntax for method calls…

Uses your system voice; voice and rate in settings.

Snapshot

≈ 3 min read

Names in other languages

No names in other languages are held for this entry yet.

Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.

Uniform function call syntax (UFCS) or uniform call syntax (UCS) is a programming language feature in D, Nim, Koka, Effekt, , Lean , and other programming languages, that allows any function to be called using the syntax for method calls (as in object-oriented programming), by using the receiver as the first parameter and the given arguments as the remaining parameters. The same technique is used in the AviSynth scripting language under the name "OOP notation".

UFCS is particularly useful when function calls are chained (behaving similar to pipes, or the various dedicated operators available in functional languages for passing values through a series of expressions). It allows free functions to fill a role similar to extension methods in some other languages.

Another benefit of the syntax is related to completion systems in IDEs, which use type information to show a list of available functions, dependent on the context. When the programmer starts with an argument, the set of potentially applicable functions is greatly narrowed down, aiding discoverability. int first(int[] arr) { return arr[0]; } int[] addone(int[] arr) { int[] result; foreach (value; arr) { result ~= value + 1; } return result; } void main() { auto a = [0, 1, 2, 3]; // all the following are correct and equivalent int b = first(a); int c = a.first(); // chaining int[] e = a.addone().addone(); } type Vector = tuple[x, y: int] proc add(a, b: Vector): Vector = (a.x + b.x, a.y + b.y) let v1 = (x: -1, y: 4) v2 = (x: 5, y: -2) # all the following are correct v3 = add(v1, v2) v4 = v1.add(v2) v5 = v1.add(v2).add(v4) Until 2018, it was common to use this term when actually referring to qualified/explicit path syntax and most commonly the fully qualified path syntax: because it is possible to have several traits defining the same method implemented on the same struct, a mechanism is needed to disambiguate which trait should be used.

Member functions can also be used as free functions through a qualified (namespaced) path. The term UFCS is incorrect for these uses, as it allows using methods as (namespaced) free functions, but not using free functions as methods.

Text derived from https://en.wikipedia.org/w/index.php?oldid=1356535537 under CC BY-SA 4.0; modifications have been made.

Sources cited in this revision

13 named source(s) extracted from the cited revision. A source with no author is shown by its publication; nothing is invented.