Redefine the LLDB_RECORD macros in terms of a common uber-macro to reduce code duplication across them.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
This looks even better than I hoped. I think this is a worthwhile simplification even without the followup patches. Just a couple of questions inline...
| lldb/include/lldb/Utility/ReproducerInstrumentation.h | ||
|---|---|---|
| 116–130 | Could you merge these two in a similar way as well (not with the method macros, just with themselves)? I know that the constructors could be implemented as a function in the other patch, but I have a feeling it will be pretty confusing if two very similar functionalities were implemented in completely different ways... | |
| 132 | idea: Should we standardize the name of the inner class and drop the Method argument? | |
| 749–752 | Why the void overload? It looks like the templated version would work just fine for void too... | |
Could you merge these two in a similar way as well (not with the method macros, just with themselves)? I know that the constructors could be implemented as a function in the other patch, but I have a feeling it will be pretty confusing if two very similar functionalities were implemented in completely different ways...