cplusplus / cplusplus/draft

[temp.spec.partial.general], [temp.expl.spec] "Partial specialization" and "explicit specialization" should be defined

Open
#7,349 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

I have noticed that we don't ever define these terms:

https://github.com/cplusplus/draft/blob/9dc7b3f30d2971ccb3bb38483a7cdb62065a2c3c/source/templates.tex#L3290-L3291

https://github.com/cplusplus/draft/blob/9dc7b3f30d2971ccb3bb38483a7cdb62065a2c3c/source/templates.tex#L6524-L6525

I imagine it would be better normatively if these terms were formal. Furthermore, I find it annoying that I can't Ctrl+F in the index and find explicit specialization or specialization, explicit that way.

Is there some reason why we don't do \defnadj{partial}{specialization} or something?

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 with source/templates.tex at the two referenced locations around lines 3290 and 6524, and inspect nearby terminology definitions and index entries. Determine how the draft formalizes these terms and whether both “partial specialization” and “explicit specialization” should be defined and indexed; done means the terms are normatively defined and searchable in the generated index.

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.