It doesn't need the entire codebase, it just needs the call map, the function signatures, etc. It doesn't have to include everything in a call - but having access to all of it means it can pick what seems relevant.

▲

danielbln a year ago | parent | next [-]

Yes, that's exactly right. The LLM gets a rough overview over the project (as you said, including function signatures and such) and will then decide what to open and use to complete/implement the objective.

▲

otabdeveloper4 a year ago | parent | prev [-]

In a real project the call map and function signatures are millions of tokens themselves.

▲

exe34 a year ago | parent [-]

For sufficiently large values of real.

▲

otabdeveloper4 a year ago | parent [-]

Anything less is not a "project", it's a "file".

▲

exe34 a year ago | parent [-]

That's right, there is no true Scotsman!

▲

otabdeveloper4 a year ago | parent [-]

Incorrect attempt as fallacy baiting.

If your repo map fits into 1000 tokens then your repo is small enough that you can just concatenate all the files together and feed the result as one prompt to the LLM.

No, current LLM technology does not allow to process actual (i.e. large) repos.

	▲	simonw a year ago \| parent [-]
		Where's your cutoff for "large"?