Gabriel Féron

I was trying to find some issues on similar behavior I'm seeing with `serde_json` (see https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=8724346d517e89cb98a054c6cfffd1cb) and came across this one. It looks like the issue is indeed with `#[serde(flatten)]`.

Is there a way we could get this merged in the 1.2.x branch with a new release on crates.io? As pointed out previously, this prevents building `x25519-dalek` with other crates...

@benesch sorry to ping you like this, but I believe this is quite an important bug fix that would make sense to review/merge, thanks!

I would even go further and add a Makefile to do all of this in one command. It can even be properly documented with very exhaustive comments.

I'm curious, do you already have something that we could commit to produce performance figures? i.e. compare C++ implementation vs the Python implementation with different Python runtimes (CPython, PyPy, ...)

I think it's a great approach to the problem: it's a nice solution for someone who wants to implement a smarter cache or as you mentionned, a no-op one.

@meh (looks like you're the new maintainer, congrats 🥳) could you give this a look?

@vext01 this is exactly what we're looking for as well (customizing the `rpath` dynamically when building in a development environment).

Thanks for the quick and detailed answer! The only problem I have right now is that `master` already has something that could work for us, but won't work with Bazel...

I'm trying to package `python-uranium` for `cura` 4.5 and 4.6 for Fedora, and I'm getting the same segfault. I'm currently trying to investigate but came to the same conclusion as...