Stephanie Wilde-Hobbs
Stephanie Wilde-Hobbs
@straight-shoota this is very standard behaviour. Almost all programs with subcommands have this. Including `crystal` itself (`-h` and `-v`).
Hi, a code sample would be needed to see what's really going on here. A stack trace doesn't tell us enough on its own.
Why can't scry implement this internally? Does scry actually shell out to `crystal tool implementation`?!
I don't understand that... the compiler has to do the same amount of work as scry, and use the same memory, so where's the benefit to shelling out??
But you reach the same peak memory consumption either way. It's just you've moved the memory usage into `crystal` instead of `scry`. How is that a real benefit? And the...
So scry doesn't do anything fancy and breaks as soon as there's a syntax error in your code. Oh well, not a very useful tool after all.
It's not useful for your find references or your go to implementation or for all of your "smart features" to break as soon as your code stops compiling. You need...
@faustinoaq I don't think you understood my point. Scry keeps running when your code doesn't compile, but does it *return results*? If not, it's fairly pointless.
@faustinoaq you're missing my point again. I don't want to get the compile error back. I want to get the same result as if the code compiled. If you go...
The way you described it working implied that that can't work.