Jump to content

Uniform function call syntax

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Shenme (talk | contribs) at 04:17, 12 August 2018 ("followings" -> "following"). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Uniform Function Call Syntax (UFCS) or sometimes Universal Function Call Syntax is a programming language feature in D and Nim 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.[1] UFCS is particularly useful when function calls are chained[2] (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 method call syntax is use with "dot-autocomplete" 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,[3] aiding discoverability.

C++ proposal

It has been proposed (as of 2016) for addition to C++ by Bjarne Stroustrup[4] and Herb Sutter[3], 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);[5] however, this leads to excessive coupling between classes.[6]

Rust usage of the term

Until 2018 it was common to use this term when actually referring to the Fully Qualified Syntax for Disambiguation. In Rust many traits can implement functions with the same name for a given type, so a mechanism is required to tell the compiler which one it should use. However it's a very specific feature that only applies to trait functions but not to free or member functions.

Examples

D programming language

import std.stdio;

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();
    int d = a.first;

    // Chaining
    int[] e = a.addone().addone();
}

Nim programming language

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)
 
  v3 = add(v1, v2)
  v4 = v1.add(v2)
  v5 = v1.add(v2).add(v1)

See also

References

  1. ^ "Functions - D Programming Language". Dlang.org. Retrieved 1 October 2017.
  2. ^ "Programming in D - Universal Function Call Syntax (UFCS)". Ddili.org. Retrieved 1 October 2017.
  3. ^ a b ""Unified Call Syntax"" (PDF). Isocpp.org. Retrieved 1 October 2017.
  4. ^ ""UFCS proposal"" (PDF). Open-std.org. Retrieved 1 October 2017.
  5. ^ "using intellisense". Msdn.microsoft.com. Retrieved 1 October 2017.
  6. ^ ""How Non-Member Functions improve encapsulation". Drdobbs.com. Retrieved 1 October 2017.