Re:Writing Iterators in Julia 0.7
by abakus on Friday July 06, 2018 @01:57PM
(#17473616)
Code with a mix of Y%#$ and lower_UPPER_CamelCase looks ugly.
[ Parent
| on HN ]
Every language looks ugly to someone who doesn't need it ;)
I have learned to ignore the inconsistencies in the languages that I have to use, especially if it's for a paying gig. Otherwise I would go crazy! Every single language has them, I'm not kidding.
Re:Writing Iterators in Julia 0.7
by s-shellfish on Friday July 06, 2018 @07:46PM
(#17475982)
That's a nice practice
The naming conventions are all very sensible, but I can see how it looks funny if you aren't fluent in Julia.
In case anyone doesn't know, the Julia convention is:
UpperCamelCase: modules & types
snake_case: variables and functions
This convention is shared, for example, with elixir (also FP Lang)
Also bang_functions! By convention, not enforced, indicate that the function may mutate one of its passed parameters. (Taken from Ruby's "be careful with this member function" idiom)
@at_sigil: macros (enforced by the language)
Ruby uses the same convention. (excluding macros, and adding question_mark_predicates?) I've seen C++ projects that adopt the same style. I don't see what's so objectionable about it.
Its also very similar to many opinionated Python style guides (minus the !, and where @ is used for decorators [which are a bit meta like macros])
Just wait until you see Julia's unicode input - you can use pretty emojis instead of ugly "Y%#$ and lower_UPPER_CamelCase"!
Fairly subjective, it is easily readable at least.
Less so when you see strongly typed system which _you_ authored which is every bit as native as the 'Native' type system we sometimes wish other languages we use in practice had at all.
> Code with a mix of Y%#$ and lower_UPPER_CamelCase looks ugly.
What is Y%#$?
Re:Writing Iterators in Julia 0.7
by simonbyrne on Friday July 06, 2018 @05:31PM
(#17475295)
Well, in Julia it's an incomplete expression (Y is a variable, % is the infix operator for remainder, and # a line comment (the $ is used for string/command interpolation, but is commented out).
Given that some of the characters in the original were italicised, I think that there were probably some stars in there that Markdown ate. My question wasn't really what operation it performs or tries to perform, but rather what abakus (https://news.ycombinator.com/item?id=17473616) meant by comparison with lower_UPPER_CamelCase.