Crystal's take on Ruby's require/include?


#1

Hi Everyone,

I’m wondering what the Crystal philosophy is about these. IMO, it’s a weak area of Ruby: string-based module references, and the system actively prevents selection inclusion into the current namespace. Does Crystal adopt the Ruby semantics and behavior, or does it aim to improve on it?