Niko Matsakis

2020-09-21: We have entered the "const evaluatable" check that allows you to have array sizes beyond `[u8; N]` (e.g., `[u8; N+1]`), but still lots of work before that would be...

@RalfJung opened https://github.com/rust-lang/rfcs/pull/3016 with the following summary: > Define how UB during const evaluation is treated: some kinds of UB must be detected, the rest leads to an unspecified result...

(To be clear, in the example that @arielb1 added, the `drop` is something more like `std::mem::drop(inner_ref)`, and not the *MIR* drop operation. Or else I am confused.)

> The drop at the unwind path looks like it might be a hard nut to crack - there's only 1 unwind path for the function, ending at the single...

@arielb1 ok, so the problem is that in bbU2, we have incoming branches from both bb2 (where the DROP would occur) and bb4 (where it would not)? In other words,...

@arielb1 so I was talking about this issue with @pnkfelix and it got me thinking. It seems to me that if we do a simple is-initialized analysis, we will have...

@arielb1 ok -- I was imagining we might do a "must be moved" analysis first, and then use the results of that to inform the liveness (i.e., if a variable...

Yeah, NLL is not the best name, though it fits in the Rust tradition ([IMHTWAMA](http://smallcultfollowing.com/babysteps/blog/2012/11/18/imagine-never-hearing-the-phrase-aliasable/) anybody?). This is sort of an "internal" feature -- i.e., once the feature gate is...

Not sure if it is relevant, but here is my integration of futures into Rayon: https://github.com/nikomatsakis/rayon/pull/193 This permits you to do things like: ```rust rayon::scope(|s| { s.spawn_future(...some future...); }); ```...

The foundation will be reviewing the trademark policy, but it will ultimately be up to the board to decide the terms that are selected.