Use of abbreviations and jargon

I assume that the use of abbreviating statement as stmt is for CPython compatibility. Another reason might be that it's slightly less to type but I think that's no longer a big concern, now that we have powerful IDEs like rust-analyzer.

The downside I see with using abbreviations (and chargon) is that it increases the barrier for new contributors for RustPython or downstream crates. Some of them may never have heard of stmt or what an expr is and it takes them, maybe only a little, time to understand that it is an abbreviation for statement.

That's why we at rome had the following two philosophies when it comes to naming:

• Utilize verbosity when naming commands and flags. No unnecessary and confusing abbreviations.
• Reduce jargon. Don’t assume that users will understand specific terminology. Strive to provide clear meaning for experts and beginners. For example, use “character” where you would traditionally use “token” when producing parser errors.

I'm curious to hear your perspective on this subject.

Aucun fichier, test ou point d’entrée n’est indiqué. Commencez par examiner la discussion de l’issue et convenir avec les maintainers de déterminer si une politique de nommage ou un périmètre concret de renommage est souhaité. Pour considérer le travail comme terminé, il faudrait disposer d’un périmètre convenu et de modifications confirmées par les maintainers, mais l’issue ne définit pas de cible d’implémentation.