News for hackers. Stuff that matters.
Re:Pyre: Fast Type Checking for Python by coldtea on Saturday May 12, 2018 @07:15AM (#17053506)
>Your classification is based on a trivial expression involving primitive types.

It's not "his classification", just his example.

The classification is established terminology in Computer Science.

>Since both will likely be represented by strings, it will return garbage, "weak" in your definition.

It's not his definition, and it's not weak in this case. Weak is not about getting garbage or not, it's about the semantics of a behavior. It could be that the result of the weak behavior is exactly what one wanted (e.g. to add a string to an SQL statement -- I might be adding together SQL statements and text about them to produce a book on SQL with my script).

In any case, the SQL statement is a string in Python, not its own type, so the result will not be weakly checked, it will be strongly checked as what it is (a string) -- Python will do what it should.

Re:Pyre: Fast Type Checking for Python by willtim on Saturday May 12, 2018 @11:08AM (#17054379)
>The classification is established terminology in Computer Science

No. It is terminology used by the dynamic language communities, not by academics.

Re:Pyre: Fast Type Checking for Python by willtim on Saturday May 12, 2018 @12:41PM (#17054830)
That looks like a random list of papers. Which one are you claiming defines or even discusses "strong" or "weak" typing? AFAIK those terms have no real definition in type theory.
Re:Pyre: Fast Type Checking for Python by viraptor on Saturday May 12, 2018 @06:40PM (#17056404)
You're moving goalposts.

You said academics don't use the terms - you were given examples that do so.

None of them need to define it - if you're interested, you can do that research.

Those terms don't have definitions in type theory and that's ok. Systems defined in the type theory deal with very explicit, theoretical analysis that usually maps well only to static-strong implementations.

Re:Pyre: Fast Type Checking for Python by willtim on Sunday May 13, 2018 @02:40AM (#17057640)
Yes goal posts have been moved, but not by me. Some of those papers may informally use these terms for static types, but it is certainly not to describe characteristics of dynamic languages. AFAIK, there is no classification in computer science that describes dynamic languages in this way. This has come from the dynamic language communities. None of those papers demonstrate that it is acceptable to call Python "strongly typed", in fact quite the opposite, as the technology discussed is not available in Python. Well, not yet anyway...