- Title
- Incorrect use of term “overloaded” in description of odr-use
- Status
- cd3
- Section
- 6.3 [basic.def.odr]
- Submitter
- Nikolay Ivchenkov
Created on 2011-09-06.00:00:00 last changed 152 months ago
Messages
Date: 2012-02-15.00:00:00
[Voted into the WP at the February, 2012 meeting;
moved to DR at the October, 2012 meeting.]
Date: 2011-08-15.00:00:00
Proposed resolution (August, 2011): Change 6.3 [basic.def.odr] paragraph 2 as follows:
...A
non-overloaded function whose name appears as a
potentially-evaluated expression is odr-used if it is the unique
lookup result or it is the selected or a member of a
set of candidate overloaded functions
(6.5 [basic.lookup], 12.2 [over.match],
12.3 [over.over]), if selected by overload
resolution when referred to from a potentially-evaluated expression,
is odr-used, unless it is a pure virtual function and its name
is not explicitly qualified...
Date: 2026-07-27.15:54:01
The current wording of 6.3 [basic.def.odr] paragraph 2 uses
the term “overloaded” differently from its definition in
Clause 12 [over] paragraph 1. For example, names found by
argument-dependent lookup are not “overloaded” if they are
not declared in the same scope. The phrasing should be reconciled
between the two sections.
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-03-03 00:00:00 | admin | set | status: drwp -> cd3 |
| 2012-11-03 00:00:00 | admin | set | status: dr -> drwp |
| 2012-02-27 00:00:00 | admin | set | messages: + msg3785 |
| 2012-02-27 00:00:00 | admin | set | messages: + msg3784 |
| 2012-02-27 00:00:00 | admin | set | status: ready -> dr |
| 2011-09-06 00:00:00 | admin | create | |