Ary Borenszweig
Ary Borenszweig
Thinking a bit more about this, the main difficulty is code like this: ```crystal def foo : Float64 if something 1 else another_call end end ``` Here people will probably...
For Crystal 2.0 I'd like it if we could remove the special subtyping rules of Tuple and NamedTuple. They just make things too complex and inconsistent.
They would be normal unions. Their types wouldn't merge.
Yeah... The parser knows whether `x` is a variable or a call based on lexical information before that: if `x` was assigned something then it's a local variable, otherwise it's...
But for instance variables, I don't know. Maybe if an `initialize` has macro code then we could assume it initializes all variables and give an error later on. There are...
What about? ```crystal def run(value : Int32) v = {% if true %} value.abs {% else %} value {% end %} pp v + 10 end ```
This is why I think there's a minor issue. If you need a variable to be defined and you also need its value to depend on a compile-time value, you...
@mattrberry If you inline `update_all_fields` in `initialize` instead of calling it, it works. That problem is initializing instance vars indirectly. Maybe if you could call a macro method at compile-time...
No. There's an open issue about being able to call macro methods at compile time, but even with that it's not clear how it would improve this situation.
I think we should eventually change `HTTP::Client` so that it's fiber-safe.