iliana etaoin
iliana etaoin
> Unless the fun is in the absurdity I mean it probably is, but let's ping @aliasless and ask.
I think that sounds like it could work, yes. I don't see any downsides for my particular use cases.
The crowbar 0.3.0 milestone is still open, it's cpython-json 0.3.0 that was published :) In my experience reexporting crates back when I first developed this was difficult. This method was...
I'm definitely fine with requiring Rust 1.30 for 0.3.0 for macro re-exports :)
In terms of upstream, see #19 and... some possibly exciting news: https://github.com/PyO3/pyo3/issues/210 — looks like PyO3 is willing to part with specialization for now in order to build on stable.
> Have you started experimenting with pyo3 yet? Not at all :(
*nod* Enjoy your vacation :)
Dropping the 0.3.0 milestone while we figure out a path forward here.
Would it make sense for the python rust overhead to be benchmarked in [cpython-json](https://github.com/ilianaw/rust-cpython-json), since that seems to be where all the magic is happening? That crate doesn't have any...