Mirrors/vscode
1
0
Fork 0
mirror of https://github.com/microsoft/vscode.git synced 2025-12-28 06:31:58 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Apply suggestion from @Copilot

Browse Source 
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This commit is contained in:
Dmitriy Vasyura 2025-11-19 11:22:46 -08:00 committed by GitHub
parent 83ffc58ce3
commit d82558b521
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
.github/prompts/micro-perf.prompt.md vendored
View File

@ -20,7 +20,7 @@ If the user provided explicit list of classes or functions to optimize, scope yo
3. Optimized function or class name should have the same name as original with '_new' suffix.
4. Create a file with '.<your-model-name>.perf.js' suffix with perf tests. For example if you are using model 'Foo' and optimizing file name utils.ts, you will create file named 'utils.foo.perf.js'.
5. **IMPORTANT**: You should use ESM format for the perf test files (i.e. use 'import' instead of 'require').
5. The perf tests should contain comprehensive perf tests covering identified scenarios and common cases, and comparing old and new implementations.
6. The results of perf tests and your summary should be placed in another file with '.<your-model-name>.perf.md' suffix, for example 'utils.foo.perf.md'.
7. The results file must include section per optimized definition with a table with comparison of old vs new implementations with speedup ratios and analysis of results.
8. At the end ask the user if they want to apply the changes and if the answer is yes, replace original implementations with optimized versions but only in cases where there are significant perf gains and no serious regressions. Revert any other changes to the original code.
6. The perf tests should contain comprehensive perf tests covering identified scenarios and common cases, and comparing old and new implementations.
7. The results of perf tests and your summary should be placed in another file with '.<your-model-name>.perf.md' suffix, for example 'utils.foo.perf.md'.
8. The results file must include section per optimized definition with a table with comparison of old vs new implementations with speedup ratios and analysis of results.
9. At the end ask the user if they want to apply the changes and if the answer is yes, replace original implementations with optimized versions but only in cases where there are significant perf gains and no serious regressions. Revert any other changes to the original code.