Re: [Chicken-janitors] #1215: Warn about too specific type declarations

[Chicken Trac]

#1215: Warn about too specific type declarations
------------------------------------+---------------------
            Reporter:  syn          |      Owner:
                Type:  enhancement  |     Status:  new
            Priority:  minor        |  Milestone:  someday
           Component:  scrutinizer  |    Version:  4.10.x
          Resolution:               |   Keywords:
Estimated difficulty:  hard         |
------------------------------------+---------------------

Comment (by evhan):

 I added this feature, but it produces far too many warnings. Stuff like
 this:

 {{{
 Note: at toplevel:
   declared type `(procedure chicken.base#error (* #!rest *) noreturn)' of
 toplevel variable `chicken.base#error' is more specific than inferred type
 `(procedure chicken.base#error (#!rest) . *)'

 Note: at toplevel:
   declared type `(procedure chicken.base#void (#!rest *) undefined)' of
 toplevel variable `chicken.base#void' is more specific than inferred type
 `(procedure chicken.base#void (#!rest) *)'

 Note: at toplevel:
   declared type `(procedure chicken.base#sleep (fixnum) undefined)' of
 toplevel variable `chicken.base#sleep' is more specific than inferred type
 `(procedure chicken.base#sleep (*) *)'
 }}}

 We could add all sorts of rules about whether to issue a warning or not in
 order to cut down on the noise, but I'm not sure this feature would be
 worth the added complexity. Plus, we already issue a warning when the
 types are ''incompatible'', so I'm more inclined to just close this
 wontfix.

--
Ticket URL: <https://bugs.call-cc.org/ticket/1215#comment:2>
CHICKEN Scheme <https://www.call-cc.org/>
CHICKEN Scheme is a compiler for the Scheme programming language.