These are chat archives for evhub/coconut

Dec 2016
Evan Hubinger
Dec 01 2016 00:49
@Nexus6 @eshansingh I love to see the debate going on here! I think this is a really important issue regarding the direction of Coconut development, and I'm glad to see everyone so engaged. I think a large part of the reason Python was so successful in the first place was because it was so approachable. Furthermore, Coconut is never going to be as good as Haskell at pure FP, so it's fortunate that Coconut's goal isn't to do that. Instead, Coconut's goal is to do the same thing Python did for OOP--make it really easy and accessible--for FP. Every feature that I implement is, in the end, geared toward achieving that goal. To that end, as far as typing is concerned, I think trying to implement an entire Hindley-Milner type system (what Haskell uses) is a bad idea, because it would make writing statically typed code harder and less accessible. On the other hand, making it easier to write MyPy type definitions makes writing statically typed code easier and more accessible, and is thus something that I support.
Niall Robinson
Dec 01 2016 11:24
do i need to compile a coco file in order to import it to another coco file?
im currently running with the -rn flags
which stops it finding the module
i just tried removing them and it works - is this desired behaviour?
(p.s. thanks for the rubber ducky debugging)
Evan Hubinger
Dec 01 2016 19:58
@niallrobinson Yes, you need to compile files to be able to import them. The idea is that compilation is slow, so if Coconut tried to do it at import time, the language would take a huge hit to performance. I'd recommend cutting the -n flag from your invocation, that way Coconut will be able to recompile any changed files when you run them.