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/
yes @mverzilli that's what I was thinking too
Flow is a huge attempt at reverse engineering common patterns of use in JS and type-check them
well "reverse engineering" is a very poor choice of terminology :P, it'd be more "capturing"
I've seen it used in some issues as a way to mess with the definition of
main
but I don't fully understand how that works
can someone help explain the usage of
funoutside of alibdeclaration to me?
I think the fun usage outside libs is very limited, fun doesn't support overloading and only support basic types, I think it is more like a C function, thinking on shared libraries or similar stuff.
By example an use case is Writing a dynamic library in Crystal, and calling it from C
@bew Sorry for the late reply. Yes I saw your wiki - pretty good. I didn't do so much research. I knew that I wanted to parse PEGs, and I liked the DSL of Parslet. I looked at D's Pegged, Clojure's Instaparse, Haskell's Earley and a couple from Go. Although I didn't spend much time ruminating and went to implementation.
I am now trying to install Crystal via Linuxbrew
I think we should include it to the book
Why did I add --with-llvm option
I am so piΕman :(
Yep
that explains
<femto> class Hierarchy def foo end def self.methods {{@type.methods}} # using all_subclasses for illustration end end class A < Hierarchy; end class B < A; end class C < B; end puts Hierarchy.methods
<femto> how do I get all the methods of a class?
<Groogy> doesn't it show there?
<femto> Syntax error in expanded macro: macro_4594465744:1: can't define def inside def [def foo ^ ================================================================================ {{@type.methods}} # using all_subclasses for illustration
<femto> in src/hello2.cr:11: macro didn't expand to a valid program, it expanded to: ================================================================================ -------------------------------------------------------------------------------- 1. [def foo 2. end]
<Groogy> you probably have to do something more sensible than {{@type.methods}} since that probably just expands into the methods own defintion it seems
<Groogy> methods is a collection of ASTNodes is my guess you probably have to create a macro that converts them to like an array of strings
<Groogy> or similar