rust-lang / rust-lang/fls

"Adjusted call operand" needs a definition

Open
#465 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-method-call C-enhancement S-waiting-on-author
Dominant language
reStructuredText
Stars
497
Forks
41
Avg merge
3h 52m
Merged PRs (30d)
4

Description

§6.12.1:8 (fls_7p6zrjbpj0kl) and §6.12.1:15 (fls_ggr5i91vur0r) describe the process of evaluating a call expression using the notion of an "adjusted call operand".

The glossary only says "An adjusted call operand is a call operand with possible auto dereferencing adjustments." The term "auto dereferencing adjustments" is not defined.

Something needs to describe the runtime behaviour of auto-deferencing, parallel to the description of the compile-time behaviour in §14.9.3 (fls_ZjJ7y9r6QQMW).

That is, something needs to say that deref or * is applied in sequence to a chain of values, corresponding to the chain of types described in §14.9.3 .

Further, depending on how "adjusted call operand" ends up being defined, the text might need to read call(&adjusted_call_operand … and call_mut(&mut adjusted_call_operand … rather than call(adjusted_call_operand … and call_mut(adjusted_call_operand ….

Contributor guide

Open the contributing guide

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

Read §6.12.1:8 and §6.12.1:15, the glossary entry for “adjusted call operand,” and §14.9.3, especially anchors fls_7p6zrjbpj0kl, fls_ggr5i91vur0r, and fls_ZjJ7y9r6QQMW. Define the runtime auto-dereferencing behavior consistently with the compile-time description, then verify whether the call and call_mut wording needs adjusted references. Done means the term and any affected expressions are unambiguous.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.