Unify `ExceptionSpecification` and `NoexceptSort`
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- tex
- Domain
- documentation
Research direction
Start by locating the definitions of ExceptionSpecification and NoexceptSort in the specification sources and compare their effects and semantics. Determine the intended unified concept and update the relevant specification text; done means the two concepts are consistently represented without losing their stated distinctions.
Written by the indexing model from the issue text.
Description
ExceptionSpecification and NoexceptSort are very close in effects and semantics. Unify them.
- Dominant language
- TeX
- Stars
- 95
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/ifc-spec
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in microsoft/ifc-spec
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ianktoo/project-monitor#14 ·
-
documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
steerion-labs/bounded-agent-runtime#93 ·
Maintainers usually reply within 1 day
-
documentation P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
:watch: Not Triaged dotnet-csharp/svc fundamentals/subsvc
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
daniel-ospina/tortoise#9038 ·
Maintainers usually reply within 1 day