Zac Nowicki

In other libraries I've written for REST APIs, I've created a namespace for functions that generate `HTTP::Request`, for example: ```cr # request.cr module Request extend self def get_resource(param) params =...

A few - meew0 was going to make one ([link](https://github.com/meew0/l-)), as well as b1nzy at one point I think. Maybe others. None to my knowledge are functional for any serious...

Great! :heart: Take your time.

@unreadable Sam just dropped a comment on my issue #9 the other day, I don't think he's gotten around to reviewing this yet. If you'd like to review it /...

Regardles of HTTPS, it is not safe to do this with an instance of `HTTP::Client` and ensure correctness. `HTTP::Client` is not "fiber-safe" as-designed, as you have found out - but...

(Context: I am one of the authors of the library being used here) This is the code in question: ```cr module Commands extend self def ping(payload : Discord::Message) puts Discord.client.create_message(payload.channel_id.value,...

@venomc312 As far as I can tell thus far, Crystal is generating some bad code for this mechanism you've written. As workaround, please take an alternate approach. There are many...

Ok, I am *fairly* certain this is an accurate reduction. ```cr struct Data getter int : UInt64 getter _pad1 : UInt64? # NOTE(z64): removing this line fixes the issue getter...

@venomc312 The problem isn't with the message payload from the event - it is with the return type of `create_message`, which returns the created message. By writing `puts Discord.client.create_message(...)` you...

@venomc312 We have a minimal reproduction now that doesn't require your code. It is fine if you want to remove it.