How C++ Resolves a Function Call

Re:How C++ Resolves a Function Call by WalterBright on Tuesday March 16, 2021 @09:41PM (#26485533)

I use the typedef version to head off problems. Anyhow, how about this:

C++:

    template<class T> T func(T t) { ... }

    T func(T)(T t) { ... }

C++:

    void f(long);

    void test() {
        f(1); // calls f(long)
    }

    void f(int);

    void f(long);

    void test() {
        f(1); // calls f(int)
    }

    void f(int);

C++:

    int f(int a[3]) { return a[4]; } // undefined behavior

    int f(int[3] a) { return a[4]; } // index out of bounds error

Of course, you can use `array<int>` in C++, and all the above can be worked around, but it just is more work and doesn't look as good.

[ Parent | on HN ]

Re:How C++ Resolves a Function Call by ncmncm on Wednesday March 17, 2021 @03:50AM (#26487738)

C++20:

  template <typename T> T func(T t) { return t; }
  auto func(auto t) { return t; }  // same, "abbreviated"

C++ is often not as nice to type as D, or as Rust. That's backward compatibility for you. But having literally tens of billions of lines of code in production, and millions of programmers who know how to use it, counts for a lot.

[ Parent | on HN ]