microsoft / microsoft/ApplicationInspector
Convert Boundary Object to use `long` instead of `int`
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C#
- Stars
- 4.4k
- Forks
- 366
- Avg merge
- 6d 7h
- Merged PRs (30d)
- 3
Description
The latest versions of YamlDotNet use long instead of int for the index of yaml token objects, to be able to handle very large files. For now these are being cast to ints to keep the existing API surface, but the Boundary object should have its internal fields converted to long to be able to support those long files as well.
Contributor guide
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
No file or test is named. Start by locating the Boundary object and its internal int fields, then trace how YamlDotNet token indexes reach them. Done means those internal fields preserve long indexes for very large files while the existing API surface remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100