cplusplus / cplusplus/draft

[over.best.ics.general] The wording about implicit conversion sequence is inconsistent

Open
#5,371 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TeX
Stars
221
Forks
813
Avg merge
16h 4m
Merged PRs (30d)
36

Description

[over.best.ics.general] p6 says

When the parameter has a class type and the argument expression has the same type, the implicit conversion sequence is an identity conversion.

However, we specify the well-formed implicit conversion sequences in [over.best.ics.general] p3 as the following:

There is no identity conversion in the list. [over.best.ics.general] p8 says

If no conversions are required to match an argument to a parameter type, the implicit conversion sequence is the standard conversion sequence consisting of the identity conversion ([over.ics.scs]).

I think we should consistently use the wording in a similar manner to [over.best.ics.general] p8. That is, we should explicitly say what the kind of the implicit conversion sequence is and then specify what the conversions the sequence comprises. Such as:

When the parameter has a class type and the argument expression has a derived class type, the implicit conversion sequence is a standard conversion sequence consisting of the derived-to-base conversion from the derived class to the base class.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing [over.best.ics.general] p6 with p8 and the list of permitted implicit conversion sequences in p3. Update the inconsistent wording so each case identifies the sequence type and its conversions, then review the surrounding paragraphs to confirm the terminology is consistent.

Written by the indexing model from the issue text.

Assessment

Tech stack
tex
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.