I've put up a patch to extend the documentation: https://reviews.llvm.org/D70252
Please have a look let me know if you have any comments or suggestions!
On Thu, Nov 14, 2019 at 9:17 AM Jonas Devlieghere wrote:
>
> Hey António,
>
> If I understand correctly, you're trying to mix between two versi
Hey António,
If I understand correctly, you're trying to mix between two versions
of the Python interpreter and library. That's not something that's
supported and has always been an issue. Internally we get the
occasional bug report where somebody install python via homebrew or
python.org and the
Ok, sounds good.
> In the base class case we already import minimally (I think), but even
minimal import causes full import
This is deliberate. During construction of ASTImporter the minimal import
flag is set. And then when ASTImporter::ImportDefinition is called, it will
do a full import, even t
Hi Gabor,
I was thinking about a different idea: perhaps we could try to track on
lldb side which recorddecls were requested to be completed during a
particular parsing session and only import full definitions if they were
requested in this session. If completion was not requested in this session,
Hi Jaroslav,
Thank you for digging into this. I think it may be possible to not eagerly
import a RecordDecl. Perhaps we could control that from
clang::ASTNodeImporter::VisitPointerType and instead of a full import we
could just do a minimal import for the PointeeType always. Similarly to
referenc