Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Fix warnings: -Wsubobject-linkage & -Wreturn-type #232

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ctrlcctrlv
Copy link
Contributor

@ctrlcctrlv ctrlcctrlv commented Nov 12, 2022

Silences these two warnings:

  • In file included from ./linuxdeploy/src/appdir_test_main.cpp:10:
    ./linuxdeploy/src/core/appdir.cpp:100‌:27: warning: ‘linuxdeploy::core::appdir::AppDir::PrivateData’ has a field ‘linuxdeploy::core::appdir::AppDir::PrivateData::copyOperationsStorage’ whose type uses the anonymous namespace [-Wsubobject-linkage]
  • In member function ‘pipe_reader::result pipe_reader::read(std::vector&, std::chrono::milliseconds)’:
    ./linuxdeploy/src/subprocess/pipe_reader.cpp:59:1: warning: control reaches end of non-void function [-Wreturn-type]

./linuxdeploy/src/core/appdir.cpp:100:27: warning:
‘linuxdeploy::core::appdir::AppDir::PrivateData’ has a field
‘linuxdeploy::core::appdir::AppDir::PrivateData::copyOperationsStorage’
whose type uses the anonymous namespace [-Wsubobject-linkage]

./linuxdeploy/src/subprocess/pipe_reader.cpp: In member function
‘pipe_reader::result pipe_reader::read(std::vector<char>&,
std::chrono::milliseconds)’:
./linuxdeploy/src/subprocess/pipe_reader.cpp:59:1: warning: control
reaches end of non-void function [-Wreturn-type]
@@ -32,7 +32,7 @@ using namespace cimg_library;

namespace fs = std::filesystem;

namespace {
namespace private_items {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change makes no sense in this context. I need to think about this...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants