Re:Julia's Arraypocalypse Release
by StefanKarpinski on Sunday September 27, 2015 @12:42PM
(#10287063)
This StackOverflow answer may help clarify things: http://stackoverflow.com/a/28096079/659248. Making return types work well with multiple dispatch is not so simple; we feel that it's better to wait to add that feature and get it right than to rush things and have to fix it later. Some background, context and tentative plans for return type annotations: https://github.com/JuliaLang/julia/issues/1090.
Re:Julia's Arraypocalypse Release
by johnmyleswhite on Sunday September 27, 2015 @12:22PM
(#10286988)
If you'd like to know canonical programming style, you should read the code in Julia Base. Learning how to write good Julia is somewhat difficult because the language occupies an unfamiliar position between traditional static languages and traditional dynamic languages.
Can you provide some concrete examples of the functionality you're looking for? What exactly does "quick-and-dirty" code look like to you?
I don't use "quick-and-dirty" as a derogatory term, so mostly I mean no error checking for rare occurrences or not ensuring correct values are being passed through. An example would be in Python if I just write MatrixA * MatrixB without any checking. I should check that they are both matrices if that is what I want, and that is what I did for reusable code. For one-off data analysis or computation, no-checking is certainly quick.
Hopefully Julia can work out all the language features and mature into a good technical language. It would also help if there is a guide about the canonical programming style. I prefer static typing but thought using type annotation I could come close to static typing while still retain the freedom of quick-and-dirty code. I believe for the current Julia I was wrong.