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

QFlags doesn't support large (> sizeof(int)) enums

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • P2: Important
    • 6.9.0 FF
    • 6.5
    • Core: Other
    • None
    • 4bd703450 (dev), da4a6cf78 (dev), a017ee967 (dev), 7971dd213 (6.8), 0d26dc672 (dev), f85a17abe (dev), 21f04d5d2 (dev), 2effeb25c (dev), d41b87e06 (dev), 57a6e671d (dev), 094f7cab5 (dev)

    Description

      First caught in https://codereview.qt-project.org/c/qt/qtbase/+/35764, with plans to introduce support in 5.1. Then we removed indications of that plan in https://codereview.qt-project.org/c/qt/qtbase/+/54720 (not sure why, though).

      Unless we need a guarantee that QFlags<T> is the same size for all T, using underlying_type<T> instead of int for sizeof(T) > sizeof(int) seems like an easy way out.

      Attachments

        Issue Links

          is duplicated by

          Suggestion - Public suggestions QTBUG-62507 Add QFlags64

          • P3: Somewhat important - Should be fixed, but doesn't affect the release in any way.
          • Closed

          Suggestion - Public suggestions QTBUG-53178 QFlags/QFlag: Support 64bit Int

          • P4: Low - Would be nice to fix, but it's not very important.
          • Closed
          resulted in

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-129804 dumpcpp generates invalid code after the moc updates

          • P0: Blocker - MUST be fixed ASAP. This includes issues that prevent/block further Qt development; Legal issues & Serious data loss issues.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-129570 moc can no longer create meta objects for private classes (that aren't Q_OBJECT themselves)

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              thiago Thiago Macieira
              fabiankosmale Fabian Kosmale
              Vladimir Minenko Vladimir Minenko
              Alex Blasche Alex Blasche
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: