[r6rs-discuss] [Formal] Allow compilers to
reject obvious violations
Arthur A. Gleckler
arthur at zurich.csail.mit.edu
Mon Feb 26 15:31:55 EST 2007
On Feb 26, 2007, at 9:46 AM, Per Bothner wrote:
> When I change the number of parameters to a function/method (I'm doing
> so right now in the Kawa implementation) I deliberately do extra work
> so the compiler can catch the places I haven't changed. For example
> I keep the old method during testing with the 'final' keyword to make
> sure I'm changed all the inherited methods, and then I remove it to
> make sure I've changed all the call-sites.
Wouldn't a warning as opposed to an error give you the help from the
compiler that you want without forcing me to do the extra work that I
want to avoid?
More information about the r6rs-discuss