SpecDeclare is not working after recent Devel-Declare update

[andrew-grechkin]

After recent update of https://metacpan.org/pod/Devel::Declare on cpan to version 0.006022
Test2-Plugin-SpecDeclare is not working any more.

I understand that I probably should complain to the Devel::Declare author and I would do that if Devel::Declare was not marked as DEPRECATED, and I thought maybe this module should not use Devel::Declare at all if Devel::Declare is so bad as it described.

Running simple test with prove t/simple.t where:

use Test2::V0;
use Test2::Tools::Spec;
use Test2::Plugin::SpecDeclare;

tests foo {
	ok(1);
}

done_testing;

is failing with:

t/simple.t .. Useless use of a constant ("tests") in void context at t/simple.t line 7.
Useless use of a constant ("5") in void context at t/simple.t line 7.
Useless use of a constant ("7") in void context at t/simple.t line 7.
Useless use of single ref constructor in void context at t/simple.t line 7.
# No tests run!
# Seeded srand with seed '20200508' from local date.
t/simple.t .. skipped: (no reason given)

running cpanm -nq https://cpan.metacpan.org/authors/id/E/ET/ETHER/Devel-Declare-0.006019.tar.gz fixes the issue

[andk]

Please allow me to point out, that the change in Devel::Declare happened after Devel::Declare was declared deprecated. What a DeDeDeDeDe, a Delicate Devel Declare Deprecation Declaration:)

[exodist]

Unfortunately I do not have the tuits to fix/rewrite the dd based stack that makes this work. Unless someone else can submit a patch the dd change means the death of spec-declare. Would be nice if it could be made to use the builtin keywords stuff perl has, but I have this far not been able to get over the initial learning curve to make any progress on that front.

…

On Sun, May 17, 2020, 12:34 PM andk ***@***.***> wrote: Please allow me to point out, that the change in Devel::Declare happened after Devel::Declare was declared deprecated. What a DeDeDeDeDe, a Delicate Devel Declare Deprecation Declaration:) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAASBOULA6CEH3CHWDC2FRTRSA33ZANCNFSM4M4CC24A> .