Skip to content

Conversation

@eisenwave
Copy link
Member

Fixes #8241.

The introductory paragraph is misleading: we claim that the subsequent concepts are for function objects, but the very next concept is invocable, which also accepts member function pointers and data member pointers, which are callable types but not function objects.

This seems like an editorial issue, since it's just about some intro fluff, nothing of normative consequence.

@tkoeppe tkoeppe merged commit 54d9b47 into cplusplus:main Oct 31, 2025
2 checks passed
@morinmorin
Copy link
Contributor

Would "callable types, function types, and references to such types" be more accurate?

@eisenwave
Copy link
Member Author

I guess yeah. I'm pretty sure it's possible to put function references into std::invocable, but those are not defined to be "function objects".

That's a problem that also affects the contents of the subclause though, not just the intro paragraph.

@morinmorin
Copy link
Contributor

Got it, thanks for the comment! I'll create a small follow-up PR soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[concepts.callable.general, concept.invocable] "function objects" and "callable type" are too restrictive

3 participants