<FromGitter>
<mattrberry> Is it possible to get the type of the `method_missing` call args at compile-time? Looking at the docs and the source it seems like it's not, but I want to make sure I'm not missing anything
<FromGitter>
<mattrberry> I could just have method overloads for the acceptable types that allow me to do `shader.set(:foo, 0.5)`, but I thought it would be fun to mess around with the method_missing macro since I haven't done that before
<FromGitter>
<Blacksmoke16> wouldn't be easier to just have multiple entrypoint files that do this kinda stuff
<FromGitter>
<ryanprior:matrix.org> @Blacksmoke16: that's what I decided to do for now :)
<FromGitter>
<mattrberry> @ryanprior:matrix.org This might be bad, but this is how I do something like python's `if __name__ == "__main__"`: `unless PROGRAM_NAME.includes?("crystal-run-spec")`
<FromGitter>
<mattrberry> I just check if the program name includes `crystal-run-spec`
<FromGitter>
<mattrberry> Then don't run the application code when it's under test
<FromGitter>
<ryanprior:matrix.org> Thank you @mattrberry that might be helpful =D
<FromGitter>
<ryanprior:matrix.org> Separately: when using the DB module, is there a way to get it to print the query strings it sends, for debugging purposes?