[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-hackers] [PATCH] Use vertical space more liberally in some
From: |
megane |
Subject: |
Re: [Chicken-hackers] [PATCH] Use vertical space more liberally in some scrutinizer messages |
Date: |
Thu, 14 Mar 2019 13:24:40 +0200 |
User-agent: |
mu4e 1.0; emacs 25.1.1 |
address@hidden writes:
>> Hi folks,
>>
>> I've just pushed most of these patches, with signoffs, to a branch
>> called "scrutiny-message-formatting", and I think we should merge it.
>
> Thanks for doing this, I've ran the tests and so far things look good.
>
> I'm a bit concerned about the verbosity of the warnings. For generated
> code or for macro expansions, cases like
>
> (if #f ...)
>
> or
>
> (let ((a '(x . y)))
> (if (pair? a) ...))
>
> will generate lots of output that only applies to trivially optimizable
> cases. I'm fine with merging the patches but perhaps we should
> distinguish between true errors (that can't possibly work) and
> those warnings that apply to valid code but indicate redundancies.
>
Hi Felix,
I totally agree about these two cases. I'd vote for hiding these
messages altogether. Even if you're compiling with -verbose.
Maybe just show statistics for known predicate calls with statically
known results. There's already a statistic for dropped branches.
And I agree that the scrutinizer should only show warnings about
expressions it knows for sure are wrong.
Message not available
Re: [Chicken-hackers] [PATCH] Use vertical space more liberally in some scrutinizer messages, megane, 2019/03/21
Re: [Chicken-hackers] [PATCH] Use vertical space more liberally in some scrutinizer messages, felix . winkelmann, 2019/03/21