Re: STH Docs.

Hi! >> To clarify something else: I don't think combing the documentation >> to remove references to "type hint" is effort well spent. Rather >> what I meant was that in any new documentation, or if we alter an >> exiting section, we should choose a more correct terminology. > > Consistency is just as technical correctness. If the feature is > called "type hints", then all references to it should call it "type > hints"; if the feature is renamed to "parameter types", then > references to "type hints" will need to be changed to refer to that > feature. Having multiple names for it in multiple places will just > confuse users. I agree that we should use unified terminology, and I propose that terminology not to be "hinting" but "parameter typing" or "typed parameters", etc. We may add a note somewhere that it also was referred as "type hinting", for the benefit of people who heard that term, but not use it in all docs. If it's OK, I can fix the docs, shouldn't be too much problem. I just don't want to do it without consensus on the matter. -- Stas Malyshev smalyshev@gmail.com