- 
    
 User Story
        
     - 
    Resolution: Fixed
 - 
    
P3: Somewhat important
 - 
    6.0, 6.1, 6.2
 - 
    None
 
- 
        Team One Foundation Sprint 52, Team A Foundation Sprint 53, Team A Foundation Sprint 54, Team A Foundation Sprint 55, Foundation PM Prioritized
 - 
        e440fec7fc (qt/qtbase/dev) e440fec7fc (qt/tqtc-qtbase/dev)
 
I must confess that I'm new to Qt and still have a lot to learn. I already like the framework and value the API consistency. Similar stuff works similar and is similarly named. However, I always stumble over the issue that QLatin1String is a view like Q(Utf8)StringView, not an owning container, as I expected. I expected the view to be called QLatin1String_View_.
Can you please fix this inconsistency?
But instead of porting everything like s/QLatin1String/QLatin1StringView/, please provide
namespace Qt {
inline namespace string_literals {
 operator""_L1
}
}
(something I use in every project and have to define by myself), but for string literals (→QLatin1StringView) and char (→QLatin1Char).
Once you have that, I don't care what the things those operators return are named, as I won't see it in my code anymore (only in compiler error messages, but it's been years since I saw one of those ;P). I digress.
Thanks!
- resulted in
 - 
                    
QTBUG-107544 [Reg 6.3.2 -> 6.4.0] qsql_oci.cpp no longer compiles
-         
 - Closed
 
 -         
 
- split to
 - 
                    
QTBUG-103459 Provide a Clazy fixit for porting QLatin1String("foo") to "foo"_L1
-         
 - Open
 
 -         
 - 
                    
QTBUG-103508 Port QLatin1String("foo") to "foo"_L1
-         
 - Open
 
 -         
 - 
                    
QTBUG-103509 Move QLatin1StringView to its own header file
-         
 - Closed
 
 -