Hi,

My final argument is it allows us to convey better semantics. Nevertheless,
i understand these concerns; i cannot really disagree with that.

I dont think "unused variable" is a code style matter, but actually more
relates to static analysis. Which kinda raised the question; why do i have
to declare it?

Roland,




Op do 21 feb. 2019 om 17:57 schreef Dan Ackroyd <dan...@basereality.com>:

> On Thu, 21 Feb 2019 at 15:46, Roland Franssen <franssen.rol...@gmail.com>
> wrote:
> > For now, I'm aiming to get rid of "unused variable $e".
>
> You seem to be trying to alter the language to fit your code-style
> checker, rather than altering your code-style checker to fit the
> language.
>
> That seems back-to-front to me.
>
> Although there are times when having multiple ways of doing the same
> thing can be a benefit, each new way is a something else that has to
> be learned, so in my opinion they need more justification than this.
>
> > Example in the wild that could benefit from this:
>
> That code appears to be using exceptions for flow-control, which is
> often recommended to not do. Again, wanting to change the language to
> meet the needs of some code that is following a style that is
> discouraged doesn't seem the right way round to me.
>
> cheers
> Dan
> Ack
>

Reply via email to