The indexing is not holding any TU but simply indexing and then it throws the TU away. Everything is saved in a database which can be shared but I so far this is not supported. I think open the same project in different IDEs is not a common use case and we should not invest in it. There are more important tasks.
From: Qt-creator <email@example.com> on behalf of René J.V. Bertin <***@gmail.com>
Sent: Tuesday, December 4, 2018 4:23:14 PM
To: Nikolai Kosjar
Subject: Re: [Qt-creator] about the clang parser backend
On Tuesday December 04 2018 14:32:21 Nikolai Kosjar wrote:
> I'm also not sure how popular the multiple-qtcreator-instances-running
> case is as it can be problematic for settings.
KDevelop has no issues with this, as long as you don't open the same project in multiple sessions :)
> For us, as the clangbackend manages the translation units of the files
> you have open in the editor, a translation unit is the dominating unit
> consuming memory and each translation unit is quite separate/isolated
> from another (that's how libclang works), and clangbackend does not deal
> with project-wide indexing, there is not much that could be shared right
That would be a good reason not to bother. I was going to mumble something about TUs but then I remember I don't really want to know more about them :)
What's that about project-wide indexing though? How does that come into play in the context of multiple projects or sessions sharing a single clangbackend?