Juniper Tyree
Juniper Tyree
I feel like GitHub has started to rate limit my repo as the CI action just no longer even starts (e.g. https://github.com/juntyr/wasmtime/pull/23), without any notice. I'll keep an eye on...
@alexcrichton I got a full release process run to succeed: - https://github.com/juntyr/wasmtime/pull/22 is the PR which includes this PR and the extra commit https://github.com/juntyr/wasmtime/pull/22/commits/0f9c4516adabc9d65cef0da7d45699a86044f260 to allow CI to run in...
Is there any chance this PR could still be reviewed before the v23 cutoff?
> @juntyr Alex is on vacation this week, so the review will take a bit longer still. I can't really comment on what that'll do to the timing relative to...
@alexcrichton Thank you so much for your guidance and I'm excited to (hopefully) be released with v23 soon :D
Thanks for pointing me in the direction of `wit-deps lock --check`! It almost solves my usecase, but also seems to modify the `wit/deps` folder. Could the check variant ensure that...
I unfortunately also don't have the time at the moment, but I can share the code that I'm using (ignore my custom error types), which runs `wit-deps` in a tempdir...
I personally think that as long as Pyo3 still has the pre-bound methods, pythonize should probably have them as well. What about adding a gil-refs feature to pythonize that gates...
> That's a really cool idea. `consume` is also more general than `destructor` in that it doesn't necessarily "destroy" the resource, it may just change the resource's state and return...