Anonymous user
Talk:Practical numbers: Difference between revisions
→Two of many examples of using Haskell in Python.
Line 70:
: Divergent approaches are a form of '''wealth''' for Rosetta Code, not a source of threat.
:[[User:Hout|Hout]] ([[User talk:Hout|talk]]) 21:30, 1 April 2021 (UTC)
==Two of many examples of using Haskell in Python.==
Hout states that he is not using Haskell in Python below; until I show on this page what I had linked it is made too obvious for even Hout to sustain the lie.
Looking at function names used in this task and just one of the other tasks Hout has examples for Hout uses the names of many functions defined in the Haskell language in his Python, (and Applescript), examples, hiding that they are Haskell translations rather than trying to be idiomatic language entries - the kind of code the language community would have you write.
This table shows exact function names found in his examples that come with Haskell but not Python, which has it's own functional tools and library.
::{| style="text-align: left;" border="4" cellpadding="4" cellspacing="4"
|+ '''Functions defined in languages'''
|-
! Name || In Haskell || In Python
|-
| take || Yes || No.
|-
| unfoldr || Yes || No.
|-
| chunksOf || Yes || No.
|-
| primeFactors || Yes || No.
|-
| until || Yes || No.
|-
|}
Hout wants to '''pass-off''' idiomatic(?) Haskell as Python. He has denied this, and is now reduced to stating that it passes the linter; and personal jibes.
There is some progress however, Hout has taken on board that Python doesn't use Haskells <code>fst</code> function to get the first item in a Python list, for example.
I object to Houts lies and midirections in his attempts to pass off Haskell translations as idiomatic Python.
--[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 09:41, 2 April 2021 (UTC)
== Haskell type hints are not valid Python==
| |||