Anonymous user
Talk:Practical numbers: Difference between revisions
→Haskell type hints are not valid Python: Haskell isn't Python.
(→*Kick*: Language,) |
(→Haskell type hints are not valid Python: Haskell isn't Python.) |
||
Line 31:
::: Very helpful to have both versions in parallel, in the proper Rosetta manner, for comparison. They aim for different things. Clarity for the reader in one case, formal type checking in the other. Thank you for putting in the effort to learn the type-hint notation and to debug that example. Enjoy !! I look forward to seeing you use more pure value-returning functions :-) [[User:Hout|Hout]] ([[User talk:Hout|talk]]) 09:58, 1 April 2021 (UTC)
:::: In fact it looks like you've debugged all those compiler type hints – wonderful !! I hope that didn't take too long :-( [[User:Hout|Hout]] ([[User talk:Hout|talk]]) 10:05, 1 April 2021 (UTC)
::::: The Padovan example shows that you add Haskell typing to Python examples. Your snide and inaccurate comments above show that you know Python typing and choose to ignore them in favour of adding Haskell typing information. I called you on it and you try misdirection and name calling. --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 11:20, 1 April 2021 (UTC)
==Python: Comment on type hints for the functional example==
| |||