Merge lp:~aacid/mir/fix_forward_declarations into lp:mir
Proposed by
Albert Astals Cid
Status: | Merged |
---|---|
Approved by: | Alan Griffiths |
Approved revision: | no longer in the source branch. |
Merged at revision: | 2981 |
Proposed branch: | lp:~aacid/mir/fix_forward_declarations |
Merge into: | lp:mir |
Diff against target: |
83 lines (+8/-8) 6 files modified
include/server/mir/compositor/display_listener.h (+1/-1) include/server/mir/frontend/buffer_stream.h (+1/-1) include/server/mir/frontend/session.h (+1/-1) include/server/mir/shell/focus_controller.h (+1/-1) include/server/mir/shell/shell.h (+1/-1) include/server/mir/shell/window_manager.h (+3/-3) |
To merge this branch: | bzr merge lp:~aacid/mir/fix_forward_declarations |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
PS Jenkins bot (community) | continuous-integration | Approve | |
Daniel van Vugt | Approve | ||
Alan Griffiths | Approve | ||
Review via email: mp+272751@code.launchpad.net |
Commit message
Fix forward declarations so that qtmir can be built with clang
To post a comment you must log in.
I think this attempt is misguided and that you should use -Wno-mismatched -tags in qtmir.
/1/ According to the language standard there are no differences between "struct" and "class" in this (declaration) context. The only differences are in the context of definitions (of which there will only be one. So the warning is pointless.
/2/ We did try to keep clang happy for a while on Mir, but eventually ran into some standard library types that were declared "struct" in some headers and "class" in others. So problems existed outside code that we control.
So there's no advantage to using this warning, and a definite cost.