Still, it's better to mention it in the documentation with all possible
caveats. I'd appreciate if you opened an issue, linking this question.
El dom., 4 ago. 2019 a las 14:20, Marcel Timmerman ()
escribió:
> Hi all,
>
> Studying GTK::Simple if found about the existence of a routine
> DEPRECATED
I did mention at the end “that `is DEPRECATED` could use a new feature for
indicating versions.”
Perhaps
sub foo () is DEPRECATED( 'other sub', v0.17.10 => v0.20.0 ) {}
(Note that it would be a list of two things where the second is a
Pair[Version,Version])
Or just three values
sub
Hi yary,
I thought that it would be nice to give some more information to the
user at what version the deprecation is started and what the next
version would be to completely remove the software from the library. It
is also nice to the developer to be able to remove old code after
passing
GTK::Simple isn't part of the Rakudo compiler, its use and this thread
suggests a demand for DEPRECATED in public Perl6.
Could it become a module for user code to import from? Pros, cons, and what
would it take to promote it to a documented routine?
Marcel what's your use-case for DEPRECATED?
Thank you Brad for the answer, I'll better not use it then. Indeed I
found it interesting because of the version arguments one could pass to
the call, but alas...
The `DEPRECATED` function is a feature of Rakudo, not Perl6.
Which means that how it works, and even its existence could be
The `DEPRECATED` function is a feature of Rakudo, not Perl6.
Which means that how it works, and even its existence could be changed
without warning.
It was added so that the compiler and runtime can mark features of itself
as deprecated.
Because of the design of the compiler and runtime, it leaks
Hi all,
Studying GTK::Simple if found about the existence of a routine
DEPRECATED which I couldn't find in the Perl6 documents. Reading from
the code I see that it needs 3 arguments, start version of deprecation,
version when it is removed and a string like in the 'is DEPRECATED()' trait.
A
