microsoft / microsoft/vscode-cpptools
Request for Adding Value Modification in Memory View
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Feature Request
Hello Development Team,
I am reaching out as an external developer with a feature request for VSCode. I would like to propose the addition of a value modification feature in the memory view of the IDE. Currently, clicking on a specific value in the memory view triggers a memory reading process.
<-- C (readMemory-88): {"command":"readMemory","arguments":{"count":0,"memoryReference":"0xffffd556aaadf9e0","offset":131072},"type":"request","seq":88}
--> R (readMemory-88): {"type":"response","request_seq":88,"success":true,"command":"readMemory","body":{"address":"0xFFFFD556AAAFF9E0","unreadableBytes":0,"data":""},"seq":58782}
To improve the usability and efficiency of working with memory, I suggest implementing the functionality to directly modify and save values within the memory representation view. This capability is already available in popular IDEs like Visual Studio, especially for languages such as C/C++. Introducing this feature to VSCode would provide a significant advantage for developers working with memory-intensive applications.
If you find this proposal valuable, I am enthusiastic about contributing to the development of this feature. I kindly request your thoughts and feedback regarding the feasibility and potential impact of incorporating value modification in the memory view of VSCode.
Thank you for considering my suggestion.
Best regards,
Sergey Bobko
related to vscode:#187057
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 implementation files or tests are named. Start by reading the related vscode#187057 issue and tracing the existing memory view's readMemory request flow; done would mean defining and implementing a reviewed way to modify and save displayed memory values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript, vscode
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100