14:49 <riza> is there an easy way to get the compiler to tell me where the method I'm calling is defined?

14:52 <riza> I'm writing a test against a stdlib modification I've made -- the spec is running fine but I can't get the change I've made to do anything. Even dropping a 'raise' at the top of the method yields no change

14:53 <FromGitter> <Blacksmoke16> calling a diff overload?

14:56 <riza> Oh I see. The stdlib specs don't run against the source like they do in a typical project, they run against the current compiler. So it's a 2 step process, make crystal and then bin/crystal spec ...?

14:56 <FromGitter> <Blacksmoke16> prob could do something with `CRYSTAL_PATH`

14:57 <FromGitter> <Blacksmoke16> and point that at your local compiler stdlib versus the one included with the installed package

14:58 <riza> I have no problem using bin/crystal to make that work. I just didn't realize that it required doing that.

14:59 <FromGitter> <Blacksmoke16> https://github.com/crystal-lang/crystal/blob/master/bin/crystal#L141 wrapper script is setting it to the local compiler for you

14:59 <FromGitter> <Blacksmoke16> yea, stdlib dev is separate from compiler

16:29 <riza> yeah for sure, when I run bin/crystal I get the warning message about the local compiler