jyn

i suspect this is "just" a bug and the Waker commit needs to be reverted. the fact that it's related to codegen units is very convincing to me, that should...

if you want to try and keep the second optimization, you could try `left.data == right.data && (ptr::eq(left.vtable, right.vtable) || left.vtable == right.vtable)`. but given that this is triggering so...

> What’s the URL of you feed? https://jyn.dev/atom.xml. You can also go to https://jyn.dev/ and hover over each post title to see the summary as title text. > What I’ve...

here are a few concrete examples: - https://jyn.dev/build-system-tradeoffs/ - first sentence: "I am currently employed to work on [the build system for the Rust compiler](https://rustc-dev-guide.rust-lang.org/building/bootstrapping/intro.html) (often called x.py or bootstrap)."...

> Yes, but, such a change will need to be advertised in advance. Maybe a release that gives a warning that it will ignore the setting in future. that seems...

I have the same issue.

alternatively it could suggest to update the dependencies in Cargo.toml, which is what i'm about to do now, but that's hard to make copy/pasteable unless they already have cargo-edit installed.

huh. apparently `cargo pgrx new` does not error if there's already a directory there. so that's another (albeit destructive) option.

nukes the entire directory, including `src/lib.rs`. it does seem to keep new files, but any file it knows about is completely overwritten.

both of those make sense to me, but do note there's a third issue, which is that the error message has `mismatches` swapped with `cargo_pgrx_version`, so it suggests a `cargo...