This is a follow-up to code review recommendation in this PR #519
Specifically to address this concern:
#519 (comment)
Proposed Solution
Extract all empty implementation ( or Null object pattern ) classes into a separate header. Main benefit is that devs can reuse that header later on to stub their instrumentation with an "empty" instrumentation. As well as in all places of code, where API needs to pass "empty" containers - we consolidate all of them in a single place, thus providing a better structure. It would also be logically consistent to have them all in one place, so that one can include just one header in order to instrument with Null instrumentation.
This is a follow-up to code review recommendation in this PR #519
Specifically to address this concern:
#519 (comment)
Proposed Solution
Extract all empty implementation ( or Null object pattern ) classes into a separate header. Main benefit is that devs can reuse that header later on to stub their instrumentation with an "empty" instrumentation. As well as in all places of code, where API needs to pass "empty" containers - we consolidate all of them in a single place, thus providing a better structure. It would also be logically consistent to have them all in one place, so that one can include just one header in order to instrument with
Nullinstrumentation.