Re: [boost] Boost.Signals deprecation and removal

-----Original Message----- From: Boost On Behalf Of David Sankel via Boost Sent: Friday, June 8, 2018 2:40 PM

On Tue, May 29, 2018 at 11:11 PM, Tim Blechmann via Boost < boost@lists.boost.org> wrote:

...

...

This first implementation of signals has been deprecated since the 1.54 release. (When) are we going to remove it? It is under management of the CMT, and it has been deprecated for over 10 major releases. I would like to suggest we remove it in the Boost 1.68.0 release.

As Paul suggested, I'd also vote for giving a removal warning for 1-2 release cycles first, but then remove it.

...

i had been working on one project, that was never migrated from signals to signals2, as attempts to migrate miserably failed: compile times significantly increased and the msvc linker would run out of memory.

this project is currently migrated away from boost.signals (1 and 2) to a more lightweight solution (nod signals), but i can imagine that there are some projects out there which still use signals(1) and which would run into trouble when it will be removed completely.

otoh i wonder if signals1 causes much maintenance overhead, that justifies potentially breaking downstream code

A standard response to something like this is that you can maintain the Boost.Signals 1 library from within your own repository even as it gets removed from Boost.

+1.

-- David

Mike