Consider analyzing LLBC directly #3040
Description
In this Zulip thread, @Nadrieril suggested that we could simplify some extraction by invoking Charon first and then just processing the LLBC. This would make a few things easier:
- LLBC contains non-doc comments, which we currently don't parse
- This would allow us to support items nested inside function bodies, which we currently reject since we can't name them by path
- We might be able to offload more Cargo resolution logic to
charon