Audit operator<< overloads for StringBuilder and support both StringBuilderImpl implementations

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We should audit places where we define operator<< for StringBuilder and consider using a template that accepts both implementations of StringBuilderImpl.

      Today we support one StringBuilder implementation but not the other, which is annoying and can lead to inconsistent behavior or unnecessary friction when adding or reusing streaming helpers.

      Example of the issue: 

      Example-1

       

            Assignee:
            Unassigned
            Reporter:
            Andrei-Cristian Murică
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: