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

≈ 6 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,[1] Nim,[2] Koka,[3] Effekt,[4], Lean[5], 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.[6] The same technique is used in the AviSynth scripting language under the name "OOP notation".[7]

UFCS is particularly useful when function calls are chained[1] (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,[8] aiding discoverability.

Contents

Examples

edit edit source

D programming language

edit edit source 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(); }

Nim programming language

edit edit source 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)

C++ proposal

edit edit source

Proposals for a unification of member function and free function calling syntax have been discussed from the early years of C++ standardization. Glassborow (2004) proposed a uniform calling syntax (UCS), allowing specially annotated free functions to be called with member function notation.[9] In 2016 it was proposed a second time for addition to C++ by Bjarne Stroustrup[10] and Herb Sutter,[8] to reduce the ambiguous decision between writing free functions and member functions, to simplify the writing of templated code. Many programmers are tempted to write member functions to get the benefits of the member function syntax (e.g. "dot-autocomplete" to list member functions);[11] however, this leads to excessive coupling between classes.[12] This was again, in 2023, proposed by Herb Sutter[13] claiming new information and insights, as well as an experimental implementation in the cppfront compiler.

Rust usage of the term

edit edit source

Until 2018, it was common[14] 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.

See also

edit edit source

References

edit edit source
  1. ^ a b "Universal Function Call Syntax (UFCS)". Programming in D. Retrieved 1 October 2017. Wikipedia revision 1356535537, retrieved 2026-11-20
  2. ^ "Nim by Example - Procs". nim-by-example.github.io. Retrieved 2024-05-19. Wikipedia revision 1356535537, retrieved 2026-11-20
  3. ^ "The Koka Programming Language". koka-lang.github.io. Retrieved 2024-05-19. Wikipedia revision 1356535537, retrieved 2026-11-20
  4. ^ "Functions". Effekt Language. Retrieved 2025-04-09. Wikipedia revision 1356535537, retrieved 2026-11-20
  5. ^ "Structures". Functional Programming in Lean. Retrieved 2025-12-09. Wikipedia revision 1356535537, retrieved 2026-11-20
  6. ^ "Functions". D Programming Language. Retrieved 1 October 2017. Wikipedia revision 1356535537, retrieved 2026-11-20
  7. ^ "Operators". Avisynth wiki. a.function(b) is equivalent to function(a, b) Wikipedia revision 1356535537, retrieved 2026-11-20
  8. ^ a b "Unified Call Syntax" (PDF). Isocpp.org. Retrieved 1 October 2017. Wikipedia revision 1356535537, retrieved 2026-11-20
  9. ^ Francis Glassborow (2 May 2004). "N1585: Uniform Calling Syntax (Re-opening public interfaces)" (PDF). Retrieved 17 December 2018. Wikipedia revision 1356535537, retrieved 2026-11-20
  10. ^ "UFCS proposal" (PDF). Open-std.org. Retrieved 1 October 2017. Wikipedia revision 1356535537, retrieved 2026-11-20
  11. ^ "Using IntelliSense". MSDN. Retrieved 1 October 2017. Wikipedia revision 1356535537, retrieved 2026-11-20
  12. ^ "How Non-Member Functions Improve Encapsulation". Drdobbs.com. Retrieved 1 October 2017. Wikipedia revision 1356535537, retrieved 2026-11-20
  13. ^ Sutter, Herb (13 October 2023). "Unified function call syntax (UFCS)" (PDF). Wikipedia revision 1356535537, retrieved 2026-11-20
  14. ^ "Rename UFCS to accurately reflect its functionality. · Issue #1140 · rust-lang/rfcs". GitHub. Retrieved 2024-05-19. Wikipedia revision 1356535537, retrieved 2026-11-20
Programming paradigmsImperative Declarative Concurrent,
parallel Metaprogramming Separation
of concerns
Comparisons/ListsComparison (multi-paradigm, object-oriented, functional), List (OO, by type)

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