[Support: UVM]

[AndrewNolte]

In UVM, this is a common pattern:

package my_pkg;
  `include "src/some_class.svh"
  `include "src/some_types.svh"
  ...
endpackage

To properly show diags and other info for the svh files in this compilation unit, we need to make note of this pattern. One heuristic we can use is the local includes found during indexing, and then map src/some_class.svh back to the pkg's syntax tree. This will require some changes with document management in the server driver, since right now there's a 1-1 assumption for documents, syntax trees, and shallow analysis.

[AndrewNolte]

I have a draft for having the relevant documents share a shallow compilation for the package, but the file expansion work for uvm_macros.svh really bogs down the server. There's a couple solutions that should both eventually be implemented to make this usable:

• Pre-compiled headers. A more accurate name for what would be implemented with slang is pre-parsed headers- macros dumped, and cst nodes copied and grafted on. These would be keyed by file + either used defines, or the entire define map.
• Request cancellation, threaded analysis. New onChange requests would cancel older ones in progress/queued. This would also be really nice for server compilations, which can already lag the server.

[evanwporter]

Regarding the PCHs, would this be something new that is developed? Or does it already exist in slang? If it's the former, how would it be serialized (ie: as binary or JSON)? Either way it would probably require a lot of wrapper code arounds slang to enable reflection (if going that route).