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

Evaluate using std::* smart pointers in Qt APIs

    XMLWordPrintable

    Details

    • Story Points:
      40
    • Sprint:
      Qt6_Foundation_ Sprint 1, Qt6_Foundation_ Sprint 2, Qt6_Foundation_ Sprint 3, Qt6_Foundation_ Sprint 4, Qt6_Foundation_ Sprint 5

      Description

      We want to investigate a possibility of using std::*smart pointers in Qt APIs.

      There are at least two usage scenarios should be investigated:

      • Use in header files (either inline functions or template classes)
      • Use purely as implementation details (only in cpp files)
      • Use in private APIs
      • Use entirely instead of raw pointers (i.e. across library boundaries)

      The following issues should be addressed for each of the cases listed above:

      • Memory management (how do we allocate and de-allocate memory)
      • Binary compatibility (what is guaranteed by different compilers/standard libraries vendors)

      Acceptance criteria:
      Research report(s) should be provided. The report should contain:

      • Research subject
      • Research method (s)
      • Pros and cons
      • Recommendations (optional)
      • Conclusion

      Note: creating subtasks for this user story is the right thing.

      Some earlier discussions:

        Attachments

          Issue Links

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

            Activity

              People

              Assignee:
              heimrich Karsten Heimrich
              Reporter:
              heimrich Karsten Heimrich
              PM Owner:
              Maurice Kalinowski Maurice Kalinowski
              RnD Owner:
              Alex Blasche Alex Blasche
              Votes:
              2 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Gerrit Reviews

                  There are no open Gerrit changes