The Crystal programming language | http://crystal-lang.org | Fund Crystal's development: http://is.gd/X7PRtI | Docs: http://crystal-lang.org/docs/ | API: http://crystal-lang.org/api/
Ah I see. I suppose it was just mentioned in passing here or the forums then.
https://crystal-lang.org/reference/syntax_and_semantics/index.html is also very good if you haven't read thru it yet
(while writing code, because no book will teach you to do :))
I have a problem with AoC even with the language I've been using for ~20 years...not very good at human descriptions of problems with tons red herrings
I tend to use Crystal pretty often to implement math routines that I find interesting (e.g. I've recently been interested in Lucas Sequences for estimating roots), so that could also be another way to practice, if you find that interesting.
Yes, I am writing a little linear algebra library to practice, actually.
Does Crystal have the distinction of shallow vs deep copying builtin?
clone vs dup i take it?
Thanks, and the last question before lunch: Is there any way to emit the disassembly, or at the very least, the IR, of a given method (preferably the former)?
Yes, though that is foreign to me so preferably the machine code (asm)
https://forum.crystal-lang.org/t/i-am-adding-crystal-to-compiler-explorer/3416 might also be helpful
otherwise there isn't a way to output specific IR, other than the whole file afaik
Ok thanks. Nothing will beat
(disassemble name) at runtime I suppose :)
so... method overloading on works for argument and not return types?
why?
def convert(value : String) : Array(String) instead of def convert(value : String, kind : Array(String).class)
i guess it could look at each overload's return type and compare that to something? :shrug:
well, i have a bunch of those that take a string and return some other type
given that crystal already infers the return type, and it knows what type i want to assign to a given instance variable, i was hoping there was a way to elide that annoation
anyway, just got my code to pass a bunch of tests, here's what i got: https://gist.github.com/manveru/5050af58be7e36bbc9d116eb5d8eccba
maybe you can suggest some other ways to do this better :)
so to add other conversions, you'd add another
convert method to Test::Configuration instead of having them infect all other types... i guess i'm still thinking functional
for json/yaml it makes more sense, since they're already in stdlib anyway
is what i would do
it's not going to harm anything, as you're not messing with the state of the internal obj or anything
can get complicated if you need to support like
Int32 | Bool | String tho