Dylan Hitt
Dylan Hitt
Through together an example of this: `misc.go` ```golang type Cancellable struct { cancellable *C.GCancellable } func NewCancellable() *Cancellable { return &Cancellable{ cancellable: C.g_cancellable_new(), } } func (c *Cancellable) Cancel() {...
Gonna close. Adding support for context asynchronously. Thanks
We actually used to do this. I can't recall what caused us to drop it. I believe it was so we could pull something large across and keeping this behavior...
Actually I'm mistaken we actually never did this. You are right that this is more `kin-openapi` issue. If we were to deal with nested schemas in fuego we'd begin to...
😆 Well this wasn't my first time reasoning through this either it appears. https://github.com/go-fuego/fuego/pull/520/files#r2099252149
I don’t know what `tg` is. But to expand. We typically try to replicate our CI checks with a target in the repos makefile to make local development a bit...
Oh disregard my comment. We already have a benchmark target. https://github.com/go-fuego/fuego/blob/7dd81256184cc44241388db6a69464f15145df4c/Makefile#L20
Closing as https://github.com/go-fuego/fuego/pull/510 addressed this
Hmm, I looked into this some. The output seems correct. At least it aligns with [this playground](https://go.dev/play/p/oicKa9U38K). I believed you'd need [something like](https://go.dev/play/p/hco_73CZtP7) this to get the structure you desire....
OIC. You may want to base off of #319