in reply to Re: Request for Comments: More annotations for Perl plugin for IntelliJ
in thread Request for Comments: More annotations for Perl plugin for IntelliJ

Well, because at least

WARNING: Subroutine signatures are experimental. The feature may be modified or removed in future versions of Perl.

And it's not good practice to use experimental features in production code. And if I remember right, in one of the latest versions signatures syntax been changed (position). And default signatures does not supports typing. And I can't force other authors to use them, so can't have completion/navigation on their modules.

  • Comment on Re^2: Request for Comments: More annotations for Perl plugin for IntelliJ

Replies are listed 'Best First'.
Re^3: Request for Comments: More annotations for Perl plugin for IntelliJ
by Athanasius (Archbishop) on Jun 21, 2016 at 07:44 UTC
[reply]

      The point of annotations - to be able to annotate foreign modules. I can't force DBI author, for example, to annotate his methods with return values or use any signatures.

      But to make my work more comfortable and faster, I'd like to have completion and navigation wherever possible.

      With described approach, I can make file with annotations for any module and get it.

      And plugin supports default perl signatures and Method::Signatures::Simple and know how to work with them.

[reply]
Re^3: Request for Comments: More annotations for Perl plugin for IntelliJ
by Anonymous Monk on Jun 20, 2016 at 21:05 UTC
    :)

    comments or experimental feature,

    comments or experimental code,

    comments or code

    comments or code

    comments or code

    Hmm, comments just aren't code

    Is anyone (even you ) using this annotations feature? More than to simply try/test it out? That you've gotten at least one feature request about it?

    Keeping the stuff in a separate file sounds good :D

[reply]
      Actively using and no requests.
[reply]

In Section Seekers of Perl Wisdom