Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-99293

As a user of QStringBuilder, and of QString*::arg(), I wonder if the two shouldn't be using the same framework

    XMLWordPrintable

    Details

    • Type: User Story
    • Status: Open
    • Priority: P3: Somewhat important
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

       

      When nesting QString::arg() calls in QStringBuilder expressions, it currently creates a temporary QString which is then passed to the QStringBuilder framework for consideration. Internally, though, QString::arg() is also doing some calculations and then reserves sufficient size in the result QString to write everything in one allocation. That's very close to what QStringBuilder is doing, so it would be cool if these two operations would use the same framework internally, and so make an arg() nested in a QStringBuilder expression not create a temporary QString, but instead just add its parts to QStringBuilder for consideration in the overall expression.

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

            Assignee:
            cnn Qt Core & Network
            Reporter:
            mmutz Marc Mutz
            PM Owner:
            Vladimir Minenko Vladimir Minenko
            RnD Owner:
            Alex Blasche Alex Blasche
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:

                Gerrit Reviews

                There are no open Gerrit changes