forked from qt-creator/qt-creator
Port from qAsConst() to std::as_const()
We've been requiring C++17 since Qt 6.0, and our qAsConst use finally starts to bother us (QTBUG-99313), so time to port away from it now. Since qAsConst has exactly the same semantics as std::as_const (down to rvalue treatment, constexpr'ness and noexcept'ness), there's really nothing more to it than a global search-and-replace. Task-number: QTBUG-99313 Change-Id: I88edd91395849574436299b8badda21bb93bea39 Reviewed-by: hjk <hjk@qt.io>
This commit is contained in:
@@ -218,7 +218,7 @@ bool RunConfiguration::isEnabled() const
|
||||
QWidget *RunConfiguration::createConfigurationWidget()
|
||||
{
|
||||
Layouting::Form builder;
|
||||
for (BaseAspect *aspect : qAsConst(m_aspects)) {
|
||||
for (BaseAspect *aspect : std::as_const(m_aspects)) {
|
||||
if (aspect->isVisible())
|
||||
aspect->addToLayout(builder.finishRow());
|
||||
}
|
||||
@@ -580,7 +580,7 @@ RunConfiguration *RunConfigurationCreationInfo::create(Target *target) const
|
||||
|
||||
RunConfiguration *RunConfigurationFactory::restore(Target *parent, const QVariantMap &map)
|
||||
{
|
||||
for (RunConfigurationFactory *factory : qAsConst(g_runConfigurationFactories)) {
|
||||
for (RunConfigurationFactory *factory : std::as_const(g_runConfigurationFactories)) {
|
||||
if (factory->canHandle(parent)) {
|
||||
const Utils::Id id = idFromMap(map);
|
||||
if (id.name().startsWith(factory->m_runConfigurationId.name())) {
|
||||
@@ -605,7 +605,7 @@ RunConfiguration *RunConfigurationFactory::clone(Target *parent, RunConfiguratio
|
||||
const QList<RunConfigurationCreationInfo> RunConfigurationFactory::creatorsForTarget(Target *parent)
|
||||
{
|
||||
QList<RunConfigurationCreationInfo> items;
|
||||
for (RunConfigurationFactory *factory : qAsConst(g_runConfigurationFactories)) {
|
||||
for (RunConfigurationFactory *factory : std::as_const(g_runConfigurationFactories)) {
|
||||
if (factory->canHandle(parent))
|
||||
items.append(factory->availableCreators(parent));
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user