Doing so is leaking an implementation detail.
I have an implementation that uses the lld infrastructure and doesn't use a map or object::SectionRef.
Paths
| Differential D35324
Don't expose a map in the DWARFContext interface ClosedPublic Authored by • rafael on Jul 12 2017, 1:01 PM.
Details
Summary Doing so is leaking an implementation detail. I have an implementation that uses the lld infrastructure and doesn't use a map or object::SectionRef.
Diff Detail Event TimelineComment Actions Worth using the extra storage like that? I guess a type-erased range is a bit much, but what about a callback-based API? ("forEachTypeSection(function_ref<void(DWARFSection&)>)") This revision is now accepted and ready to land.Jul 12 2017, 1:55 PM
Revision Contents
Diff 106290 include/llvm/DebugInfo/DWARF/DWARFContext.h
lib/DebugInfo/DWARF/DWARFContext.cpp
|