Hey! Aaron from the Visual Studio team here, a few notes on what we've built to help iterate across multiple files:
- Added a planning step before generating code: this provides a summary that highlights affected files and proposed changes, just enough to orient you when reviewing the code-diffs.
- Added tool calling: during the planning phase, we automatically search for relevant files in your codebase that could help with your prompt.
- Added speculative decoding: quickly maps your code diffs inline, in your editor, allowing you to review with all your context. Review each chunk with the TAB key to accept or options to apply/dismiss all at once.
- Added checkpoints: allow safe rollbacks or retry if you've got a new approach.
If you're using the latest Copilot + VS to write C++, would love any feedback on how well this interaction works with C++. We've got a couple minor kinks we're working out, any scenarios/feedback you can find would be awesome.
Hey! I worked on this - yes, the method/IntelliSense selection is bound. We measure model accuracy through accept rate of predictions and we've seen a jump after introducing this.
Anything after the method/intellisense selection, however, isn't bound.
- Added a planning step before generating code: this provides a summary that highlights affected files and proposed changes, just enough to orient you when reviewing the code-diffs.
- Added tool calling: during the planning phase, we automatically search for relevant files in your codebase that could help with your prompt.
- Added speculative decoding: quickly maps your code diffs inline, in your editor, allowing you to review with all your context. Review each chunk with the TAB key to accept or options to apply/dismiss all at once.
- Added checkpoints: allow safe rollbacks or retry if you've got a new approach.
We'd love to hear what you think, feel free to tweet me here: https://x.com/aaronyim/status/1884255110949396879