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/
My first library is finished, code-wise, and I'm pretty happy with it. I still have to do docs and specs which will take a long time given the number of defs, but yay
I saved a considerable amount of complexity and duplicated code by wrapping a staticarray and forwarding missing, instead of all the nonsense i had to do before
i think srasu suggested that, or whoever it was, thanks
oh i guess it's suskeyhose over on gitter
Is there a recommended style guide apart from the rather short one on the web site? I was looking to see what magic number this language recommends for max columns :)
i usually just make it so i dont have to scroll :p
Well, I hope the macro writing DSL grammar is on the list of things to improve. This is definitely not as powerful as Lisp.
methods in macro land is the issue discussing most of my concerns though
I get that nothing can possibly be as powerful as Lisp, without actually being Lisp, because once you add homoiconicity to a language that enables powerful macros taking advantage of the full language instead of a DSL, you can practically call it a Lisp
But a little more will go a long way
However, despite being a huge Lisp fan, I stay away from macros unless I have to, unlike a lot of people that grow old trying to bend the language to do cool new things. However, when I actually do need to write a macro for some syntactic abstraction or boilerplate reduction, I need access to the language at compile time, not some tiny subset of it.
I am by no means trying to bash Crystal though. Its balance of simplicity and power is what drove me to try it, and I am very pleased with that. Lisp is pretty much 1000% power.
Yes, the "loop n times" instead of "loop over some collection/range" can be simulated like that, though I would have liked to use
_ in place of i to convey meaning to the reader.
Bringing over the
times method would almost be enough, except need some concise DSL to account for when the count is the length of a sequence, but still don't want to bind any e or i vars
</nitpick> The real issue is DRY violation as that issue discusses. I think a lot of people would be happy with work done in that area
you also have
.each and .map available
kinda
you have macro level variables that you could use it to set, but you'd have to use
for in if you wanted to iterate over them and generate code
Oh sure, that'll just return a sequence for you to do whatever with, like
{% for ... %} :)
That latest snippet answered an unrelated question I was going to ask.
I assumed right, that you can bind compile-time variables like that
https://github.com/athena-framework/dependency-injection/blob/master/src/service_container.cr#L135 also quite a bit of complex logic using this feature if you wanted to poke around
Never made the connection
code is super gross because you cant reuse anything, but it would look much better with crystal-lang/crystal#8835
haha yea it is
Sadly, I don't do any webdev these days anymore, so might use the logger or one of the decoupled things if anything.
Fair enough. Well there was one athena project i was thinking of using, but I forget what it was
other than that, can deff use them independently. E.g. like the validator or serializer etc
Which project of yours (or other) would you say has the best docs? I would like to take a look at the tricks from the masters :)
(I am not very great at writing docs, probably because I have too many forever projects to get to that point)