microsoft / microsoft/CLRInstrumentationEngine
Document use of GetReJITParameters over ReJITCompilationStarted
Open
Nobody has claimed this yet.
documentation
- Dominant language
- C++
- Stars
- 102
- Forks
- 52
- Avg merge
- 13h 11m
- Merged PRs (30d)
- 6
Description
While both work against the CLR for ReJIT, GetReJITParameters is necessary for CLRIE to be able to provide iterative IL changes (ReJITCompilationStarted would stomp over everyone's changes).
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
Start by reviewing the existing documentation for GetReJITParameters and ReJITCompilationStarted, then identify where ReJIT guidance is maintained. Done means documenting why CLRIE should use GetReJITParameters for iterative IL changes and why ReJITCompilationStarted can overwrite other extensions' changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100