[Info-vax] Rust as a HS language, was: Re: Quiet?

[Dan Cross]

In article <t2ne22$dl0$1 at dont-email.me>,
Dave Froble  <davef at tsoft-inc.com> wrote:
>>> I have caught some flack from some here for choosing to not always declare
>>> variables.  I feel that such a practice is safe, if care and tools to verify
>>> some things are in use.  The opinions of others are just that, opinions, and
>>> subjective.
>>
>> *shrug* How do your maintainers feel about that?
>
>Once maintainers are familiar with company standards and practices, they are 
>quite alright with the practice.
>
>I just don't feel I should do the grunt work when I have a compiler to do it for 
>me.  Then again, because of what I consider deficiencies in the compiler, I've 
>had to develop tools to process compiler listings looking for issues.  Damn 
>compiler has the info, it should do that work also.
>
>Another factor is, many variables are declared, for various reasons.  Not so 
>many are undeclared.

Lack of consistency creates cognitive load for readers.  Code is
read many more times than it's written or changed.

>> It's odd to me that there are folks about being facile with
>> tools and languages and hard-earned experience, yet they reject
>> the very things that collective experience has taught the
>> industry at large.  We know, for instance, that statically typed
>> languages have fewer defects than dynamically typed languages,
>> just as we know that declaring variables can serve documentary
>> and pedagogical purposes.
>
>"We know that?"
>
>I'm not so sure about that.

Fortunately, we have empirical evidence we can evaluate.

https://danluu.com/empirical-pl/

	- Dan C.