On Thu, 17 May 2018 08:14:15 +
Alex Blasche wrote:
> The naming conventions for enums state that each enum value name must repeat
> a part of the enum Type name (for details see
> https://wiki.qt.io/API_Design_Principles#Naming_Enum_Types_and_Values)
>
> In case of scoped enums this become
> On 17 May 2018, at 10:14, Alex Blasche wrote:
>
> Hi,
>
> The naming conventions for enums state that each enum value name must repeat
> a part of the enum Type name (for details see
> https://wiki.qt.io/API_Design_Principles#Naming_Enum_Types_and_Values)
>
> In case of scoped enums this
Il 17/05/2018 10:14, Alex Blasche ha scritto:
In case of scoped enums this becomes a superfluous rule as the type has to be
mentioned anyway. Does anybody object to modifying the above definition by
adding an exception for scoped enums where you do not have to repeat a part of
the enum type na
Congratulations to Mårten. The rights have been adjusted.
--
Alex
From: Development
on behalf of Edward Welbourne
Sent: Wednesday, 25 April 2018 1:40:41 PM
To: development@qt-project.org
Subject: [Development] Nominating Mårten Nordheim as an approver
Hi,
The naming conventions for enums state that each enum value name must repeat a
part of the enum Type name (for details see
https://wiki.qt.io/API_Design_Principles#Naming_Enum_Types_and_Values)
In case of scoped enums this becomes a superfluous rule as the type has to be
mentioned anyway.
On 16/05/2018, 19.07, "Development on behalf of Thiago Macieira"
wrote:
>
> To all users: please continue submitting contributions through the
>contribution system as much as you can. Submitting patches via the bug
>reporting tool may not work if the assignee or maintainer in q
