[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Navigating an enormous code base
From: |
John Yates |
Subject: |
Re: Navigating an enormous code base |
Date: |
Wed, 27 Apr 2022 18:59:11 -0400 |
Start with feeding a completion interface:
* Do you index on demand? If no, then when? And how do you
keep the index upto date?
* Indexing the entire workspace will result in an intractably
large index. So how do you partition it?
* Is the user restricted to querying a single partition of the
index? If yes, then that feels painfully restrictive. If no,
how does that user indicate which partition indices to combine?
How is combining accomplished?
* How are duplicate filenames handled?
Need I say more?
- Navigating an enormous code base, John Yates, 2022/04/25
- Re: Navigating an enormous code base, Daniel Fleischer, 2022/04/26
- Re: Navigating an enormous code base, Eli Zaretskii, 2022/04/26
- Re: Navigating an enormous code base, Stefan Monnier, 2022/04/26
- Re: Navigating an enormous code base, Marcus Harnisch, 2022/04/27
- Re: Navigating an enormous code base, mrf, 2022/04/27
- Re: Navigating an enormous code base, Emanuel Berg, 2022/04/27
- Re: Navigating an enormous code base,
John Yates <=
- Re: Navigating an enormous code base, Emanuel Berg, 2022/04/27
- Re: Navigating an enormous code base, Marcus Harnisch, 2022/04/28
- Re: Navigating an enormous code base, Leo Liu, 2022/04/28
- Re: Navigating an enormous code base, Marcus Harnisch, 2022/04/28
- Re: Navigating an enormous code base, Leo Liu, 2022/04/28
- Re: Navigating an enormous code base, John Yates, 2022/04/28
- Re: Navigating an enormous code base, Marcus Harnisch, 2022/04/28
- Re: Navigating an enormous code base, John Yates, 2022/04/28
- Re: Navigating an enormous code base, Marcus Harnisch, 2022/04/28
- Re: Navigating an enormous code base, John Yates, 2022/04/28