chakra-core / chakra-core/ChakraCore
TTD - Improve scanning of well known persistent pointers
- Dominant language
- JavaScript
- Stars
- 9.3k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
We currently use a workaround in TTRuntimeInfoTracker.cpp to scan and track well known persistent pointers. This doesn't scale well and is currently missing a number of properties on JavascriptLibraryBase.
Ideally we would like a "JsWellKnownObject" macro + list of fields that would notify us of what these fields/objects are (and give us stable names/ids for them).
See #2309 for more info.
Contributor guide
Research direction
Start with TTRuntimeInfoTracker.cpp and read issue #2309 for the background on persistent-pointer scanning. Trace how JavascriptLibraryBase properties are currently discovered, then define completion around stable names or IDs being available for all well-known persistent pointers without the current workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100