Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6146069
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T18:53:27+00:00 2026-05-23T18:53:27+00:00

A point from n3290 ISO draft: Lambda expressions : section 5.1.2, para 6: The

  • 0

A point from n3290 ISO draft:
Lambda expressions : section 5.1.2, para 6:

         "The closure type for a lambda-expression with no 
      lambda-capture has a public non-virtual non-explicit const
      conversion function to pointer to function having the same
      parameter and return types as the closure type’s function
      call operator. The value returned by this conversion
      function shall be the address of a function that, when
      invoked, has the same effect as invoking the closure
      type’s function call operator."

Can any one explain this point with an example please ?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-23T18:53:28+00:00Added an answer on May 23, 2026 at 6:53 pm

    The short answer

    This just means that lambdas not capturing anything can be converted into a function pointer with the same signature:

    auto func = [](int x) { return x * 2; };
    int (*func_ptr)(int) = func; // legal.
    
    int y = func_ptr(2); // y is 4.
    

    And a capture makes it illegal:

    int n = 2;
    auto func = [=](int x) { return x * n; };
    int (*func_ptr)(int) = func; // illegal, func captures n
    

    The long answer

    Lambdas are shorthand to create a functor:

    auto func = [](int x) { return x * 2; };
    

    Is equivalent to:

    struct func_type
    {
        int operator()(int x) const { return x * 2; }
    }
    
    func_type func = func_type();
    

    In this case func_type is the “closure type” and operator() is the “function call operator”. When you take the address of a lambda, it is as if you declared the operator() static and take its address, like any other function:

    struct func_type
    {
        static int f(int x) { return x * 2; }
    }
    
    int (*func_ptr)(int) = &func_type::f;
    

    When you have captured variables, they become members of func_type. operator() depends on these members, so it can’t be made static:

    struct func_type
    {
        int const m_n;
    
        func_type(int n) : m_n(n) {}
        int operator()(int x) const { return x * m_n; }
    }
    
    int n = 2;
    auto func = func_type(n);
    

    An ordinary function has no notion of member variables. Keeping with this thought, lambdas can only be treated as an ordinary function if they also have no member variables.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

A point from ISO draft n3290 section 3.4.2 paragraph 1: When the postfix-expression in
A point from ISO draft N3290 : Unqualified Name Lookup :section 3.4.1, para 14:
A point from ISO draft n3290 section 3.3.9 paragraph 4: The declarative region of
A point from ISO C++ DRAFT n3290 :Argument dependant Name Lookup : section 3.4.2,
A point from iso C++ n3290 :Argument dependant Name Lookup: section 3.4.2, para 4
A point from N3290 draft ISO Standard, §3.4.1/12: During the lookup of a name
A point from the ISO C++ Draft n3290 : 3.4.0 2nd point A name
A point from the ISO C++ draft (n3290): 3.4.2/3 Argument Dependant Name Lookup: Let
A point from the ISO C++ draft (n3290): 3.4.3.2/1 Namespace members If the nested-name-specifier
A point from the ISO C++ draft (n3290): 3.4.3.2/1 Namespace members For a namespace

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.