TheAngryByrd / TheAngryByrd/MrBuild
Define differential correctness for the supported F# corpus
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Part of #19
Question
For the initial MrBuild, FsToolkit.ErrorHandling, and focused-fixture corpus, what does it mean for the new engine to match FCS?
Resolve comparison rules for diagnostics, ranges, severity, hover/type display, navigation targets, completion items, incomplete code, signature files, project references, and unsupported constructs. Decide which differences are acceptable and how they are recorded rather than silently ignored.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reading issue #19 and the initial MrBuild, FsToolkit.ErrorHandling, and focused-fixture corpus described here. Define comparison rules for each listed FCS behavior, including acceptable differences and how they are recorded; done means the rules cover unsupported constructs and are no longer silently ignored.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- compilers, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100