first parameter have default values. The explicit keyword can be applied to a constructor or (since C++11) a conversion operator, to ensure that it can only be used when the destination type is explicit at at the point of use, e.g. with a cast. This applies not only to implicit conversions, but to C++11’s list initialization syntax: class Foo { explicit Foo(int x, double y); ... }; void Func(Foo f); Func({42 type appears before the function name. For example: int foo(int x); The new form, introduced in C++11, uses the auto keyword before the function name and a trailing return type after the argument list

the support of it will be removed soon. bg.. meta:: description: Guide to using features from C++11, C++14 and beyond in Krita’s codebase. Modern C++ usage guidelines for the Krita codebase Contents references) C++11 features mostly for template programming Other C++11 features that will not be useful General links about using Modern C++ in Qt There have been a few links discussing mixing C++11 with Qt Qt, and starting with Qt 5.6 C++11 support will be default. Note: there is a lot of hype about C++11, and although many of its new features are quite welcome, often the trade-offs from these changes get

the support of it will be removed soon. bg.. meta:: description: Guide to using features from C++11, C++14 and beyond in Krita’s codebase. Modern C++ usage guidelines for the Krita codebase 목차 Modern references) C++11 features mostly for template programming Other C++11 features that will not be useful General links about using Modern C++ in Qt There have been a few links discussing mixing C++11 with Qt Qt, and starting with Qt 5.6 C++11 support will be default. Note: there is a lot of hype about C++11, and although many of its new features are quite welcome, often the trade-offs from these changes get

the support of it will be removed soon. description: bg.. meta:: Guide to using features from C++11, C++14 and beyond in Krita’s codebase. Modern C++ usage guidelines for the Krita codebase ⽬录 Modern references) C++11 features mostly for template programming Other C++11 features that will not be useful General links about using Modern C++ in Qt There have been a few links discussing mixing C++11 with Qt Qt, and starting with Qt 5.6 C++11 support will be default. Note: there is a lot of hype about C++11, and although many of its new features are quite welcome, often the trade-offs from these changes get

the support of it will be removed soon. description: bg.. meta:: Guide to using features from C++11, C++14 and beyond in Krita’s codebase. Modern C++ usage guidelines for the Krita codebase 目录 Modern references) C++11 features mostly for template programming Other C++11 features that will not be useful General links about using Modern C++ in Qt There have been a few links discussing mixing C++11 with Qt Qt, and starting with Qt 5.6 C++11 support will be default. Note: there is a lot of hype about C++11, and although many of its new features are quite welcome, often the trade-offs from these changes get

the support of it will be removed soon. bg.. meta:: description: Guide to using features from C++11, C++14 and beyond in Krita’s codebase. Modern C++ usage guidelines for the Krita codebase 目录 Modern references) C++11 features mostly for template programming Other C++11 features that will not be useful General links about using Modern C++ in Qt There have been a few links discussing mixing C++11 with Qt Qt, and starting with Qt 5.6 C++11 support will be default. Note: there is a lot of hype about C++11, and although many of its new features are quite welcome, often the trade-offs from these changes get

the support of it will be removed soon. description:: bg.. meta:: Guide to using features from C++11, C++14 and beyond in Kritaʼs codebase. Modern C++ usage guidelines for the Krita codebase 目录 Modern references) C++11 features mostly for template programming Other C++11 features that will not be useful General links about using Modern C++ in Qt There have been a few links discussing mixing C++11 with Qt Qt, and starting with Qt 5.6 C++11 support will be default. Note: there is a lot of hype about C++11, and although many of its new features are quite welcome, often the trade-offs from these changes get

the support of it will be removed soon. description:: bg.. meta:: Guide to using features from C++11, C++14 and beyond in Krita’s codebase. Modern C++ usage guidelines for the Krita codebase 目录 Modern references) C++11 features mostly for template programming Other C++11 features that will not be useful General links about using Modern C++ in Qt There have been a few links discussing mixing C++11 with Qt Qt, and starting with Qt 5.6 C++11 support will be default. Note: there is a lot of hype about C++11, and although many of its new features are quite welcome, often the trade-offs from these changes get

the support of it will be removed soon. description:: bg.. meta:: Guide to using features from C++11, C++14 and beyond in Krita’s codebase. Modern C++ usage guidelines for the Krita codebase 目录 Modern references) C++11 features mostly for template programming Other C++11 features that will not be useful General links about using Modern C++ in Qt There have been a few links discussing mixing C++11 with Qt Qt, and starting with Qt 5.6 C++11 support will be default. Note: there is a lot of hype about C++11, and although many of its new features are quite welcome, often the trade-offs from these changes get

the support of it will be removed soon. bg.. meta:: description: Guide to using features from C++11, C++14 and beyond in Krita's codebase. Modern C++ usage guidelines for the Krita codebase 目次 Modern references) C++11 features mostly for template programming Other C++11 features that will not be useful General links about using Modern C++ in Qt There have been a few links discussing mixing C++11 with Qt Qt, and starting with Qt 5.6 C++11 support will be default. Note: there is a lot of hype about C++11, and although many of its new features are quite welcome, often the trade-offs from these changes get