juliehockett added a comment. > 2. I've mentioned it before as a comment, but to what extent will you be > parsing information in this frontend? Currently the links between types are > primarily stored as strings. Are you planning to have the backend that > generates the MarkDown parse those strings and link them to types? E.g. the > parenttype is a std::vector<std::string> and assuming you want the markdown > to have a link to this parent type, will the MarkDown have to parse this type > and lookup the link to the original type? Or will you embed references to > other types within the intermediate format?
This is a good question -- expecting the backend to parse the strings is a bit of an unrealistic assumption, as you point out. I'm currently switching the key type from the names to the USRs, and I think that might help resolve this too. With that, each type can reference the USR of the linked def, which can be used to directly lookup the linked def. Does that make sense? I have to see where the majority of the USR resolution should be done (i.e. here in the mapper or later in the reducer), so will update once I take a look at that. https://reviews.llvm.org/D41102 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
