Jeff Burdges

It's tricky.. I've changed my tune somewhat.. In my mind, approval checking had three advantages: First, we avoid all validators checking parathread code upgrades, but an alternative would simply be...

We might leverage the approval's logic for grandpa though: If a parachain posts a code block then we transport the code to all validators, perhaps via availability and reconstructing, and...

@AlistairStewart won't like impacting liveness but yeah I'm fine with blocking inclusions on disputes. We'll move to Sergi's deterministic WASM metering, which makes 3 less likely. We'd block only parachains...

I agree disputes spam against all parachains sounds like one attack technique. It's not 100% clear how you leverage this attack yet, and clearly the bug problem exists, hence my...

There are four ArrayVec-like crates that provide this functionality now, so zero reason for "quickly" doing "stop-gaps". If anything, we need a fifth crate that unifies their various features, ala...

Yes, it's possible they do not unify cleanly, which maybe his concern. I donno..

I've questions about https://github.com/rust-lang/rfcs/blob/c34989cc81c0dbd96ca65a50fe987ad09f5a6251/text/0000-placement-by-return.md#guide-level-explanation Is there any good reason why `good()` works but `bad()` does not work? Isn't this really just complex bug in rustc? If the return is `Sized`...

If you're worried about length then `Box::with` works fine. I think `Box::new` should always box the closure, but you could investigate reviving the `box` keyword for closures.

Aside from guarantees, there are more complex cases cases for NVRO too, so an `#[nrvo]` attribute could enforce both guarantees and express the desired NRVO structure. ``` fn foo(..) ->...

We'll eventually want compiler plugins (forks?) for various "slow" static analysis task, including refinement types, but presumably only after chalk. It'd also help prevent them from interacting with soundness. Refinements...