mirror of
https://github.com/Aider-AI/aider.git
synced 2025-05-25 06:44:59 +00:00
Update ctags.md
This commit is contained in:
parent
fbf73c4412
commit
8d18afa338
1 changed files with 1 additions and 1 deletions
|
@ -72,7 +72,7 @@ Mapping out the repo like this provides some benefits:
|
||||||
- GPT can see variables, classes, methods and function signatures from everywhere in the repo. This alone may give it enough context to solve many tasks. For example, it can probably figure out how to use the API exported from a module based on the details shown in the map.
|
- GPT can see variables, classes, methods and function signatures from everywhere in the repo. This alone may give it enough context to solve many tasks. For example, it can probably figure out how to use the API exported from a module based on the details shown in the map.
|
||||||
- If it needs to see more code, GPT can use the map to figure out by itself which files it needs to look at. GPT will then ask to see these specific files, and `aider` will automatically add them to the chat context (with user approval).
|
- If it needs to see more code, GPT can use the map to figure out by itself which files it needs to look at. GPT will then ask to see these specific files, and `aider` will automatically add them to the chat context (with user approval).
|
||||||
|
|
||||||
Of course, for large repositories, even their map might be too large
|
Of course, for large repositories, even just their map might be too large
|
||||||
for the context window. However, this mapping approach opens up the
|
for the context window. However, this mapping approach opens up the
|
||||||
ability to collaborate with GPT-4 on larger codebases than previous
|
ability to collaborate with GPT-4 on larger codebases than previous
|
||||||
methods. It also reduces the need to manually curate which files to
|
methods. It also reduces the need to manually curate which files to
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue