-
Notifications
You must be signed in to change notification settings - Fork 164
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
chore!: Deprecate any_color_converted_view #660
chore!: Deprecate any_color_converted_view #660
Conversation
Makes sense, thanks! Actually I wonder if we could remove it alltogether... |
As far as I understand Boost's policy with regards to deprecation there needs to be at least one version / release where stuff that will get removed has to be announced as deprecated. Then the next release can actually remove that stuff. So it could be something like:
|
Yes, we need to deprecate it first with a release note similar to this |
I've just created a pull request with the corresponding release notes to get things moving: #678. |
Yes, it can be closed. However, after the release of Boost 1.80 a new PR can (and should) be created that actually removes the then deprecated |
In my PR here I also changed the implementation of the functions in order to remove the invocation of #678 hasn't changed the implementation of the deprecated functions. But I can rebase #656 later on and change the implementation again if #678 gets merged. |
@marco-langer Good point. Thank you very much for your help! I'm closing this PR and I'm going to merge @striezel 's #678. |
color_converted_view has the same implementation and can be used as a replacement, providing the same functionality. This builds on #660 by @marco-langer (Thank you!) Due to the fact that the switch to C++14 has been announced in #677, we can now officially use the [[deprecated]] attribute which was standardized in C++14. This is initial part of deprecating the `any_color_converted_view` and as @marco-langer pointed in #660 (comment) there are more changes to follow.
Since #678 got merged, I noticed that the deprecation warning is triggered with some compilers even if the function is not invoked at all: #include <boost/gil.hpp>
#include <boost/gil/extension/io/png.hpp>
int main() {} Compiled with gcc 10.2.1:
This warning is not emitted with clang 11. Currently I think it is a compiler bug in gcc 10.2.1, because we never invoke the deprecated function in the given example. Actually I already noticed this behavior while working on this PR and simply forgot to mention it as we had the discussion whether to merge this PR or #678. This PR does not emit the warning. I will try to complete #656 ASAP in order to solve this new problem, but also in order to get the apply_operation deprecation shipped with Boost 1.80. |
I think you may be correct: GCC Bug 95302 - function attributed to be deprecated cannot include a typedef/using Thank you! |
Related to #660, see #660 (comment)
Description
I suggest to deprecate the function
any_color_converted_view
fromgil/extension/dynamic_image/image_view_factory.hpp
, because it has the exact same implementation as the functioncolor_converted_view
:According to the documentation of
any_color_converted_view
, the prefixany_
was added to avoid an ambiguous overload resolution for GCC 3.4, which however, we do not have to support anymore with C++11.Tasklist