Ary Borenszweig

I thought about working on this next but this program: ```noir fn main() { let bytes = [1, 2, 3]; let field = Field::from_be_bytes(bytes); } ``` crashes with the same...

Thank you for this! But the docs for that page are automatically generated from the code that contains the actual commands and flags. The docs should go on top of...

After that, _I think_ the docs need to be regenerated, there's a readme inside the docs directory on how to do that.

I wonder if we could detect that early and give a nice error message. That is, if self is used inside an initialize, check if it's used after all non-nilable...

An optional middleware stack is probably good. I saw [crystal-cossack](https://github.com/greyblake/crystal-cossack) the other day and although I like the idea, I wouldn't like thousands of HTTP clients for Crystal if we...

@greyblake Thanks for the thorough explanation! Some comments on your points: - Simple user friendly interfaces: we have `HTTP::Client.get("http://www.example.com")`. Can it be simpler than that? :-) - Middleware support: missing...

Another thing, right now the compiler complains in this case: ```crystal class Foo property x : Int32 end ``` The error is: > instance variable '@x' of Foo was not...

Ah... and the downside is that if you are defining models for consuming an API, you'll actually have to write a bit more: ```crystal require "json" class SomeModel include JSON::Serializable...

I'm thinking that allocate should add the GC finalizer, maybe. Then that problem will be solved. I think Rust needs a Serializable attribute because they don't have reflection. With reflection...

@RX14 I still don't understand how you would avoid that indirection and those extra allocations. I guess I'd have to still a proof of concept implementation to understand it :-)...