Ary Borenszweig
Ary Borenszweig
What's so bad about not using `--no-codegen` when using `--emit`? No codegen means the codegen phase doesn't run, and this trivially means no artifacts (.ll, .s, .o, final executable) will...
> True, these are all different stages of codegen. But what do you do if you want the .ll (or .s) but not .o? You just wait a little more?...
Or, well, put another one, if someone wants to implement it, please send a PR (I won't)
There's no bug. The `property` macro is defined inside an inline macro. Take a look at this code: ```crystal class Person {% begin %} macro foo def one 1 end...
There's no old behavior. The property macro was written in a different way at that time. It wasn't defined using another macro.
The tool is already recursive. Maybe the only improvement is showing "inline macro" instead of that macro_43675675 name.
I mean, if you need it to be that customizable why not write to the response by hand in that case? After all this is a convenience method for the...
Reduced: ```crystal class Base end class Child < Base end class Gen(T) < Base end def call(error : Base) end def call(error : Gen) end base = Base.new || Child.new...
This one is tough. This one and #3299 need a big rewrite of the binding system and how a call needs to be recomputed when a generic instance is created....
Also a note that I briefly thought how to implement this but I have no idea. I get confused. And I won't have time to do this. So if someone...