scottmcm

We talked about this in the lang team triage meeting today. There were some thoughts that using "fields" for arrays would be surprising to people from most other languages. There's...

@CAD97 Do you perhaps have a topic link for the discussion? The link seems to just be to the UCG stream in general.

Perhaps a silly question, but why an attribute instead of a trait? I pictured: ``` trait SerdeFinalize: Sized { fn finalize(self) -> Result; } #[derive(Serialize, Deserialize)] #[serde(Finalize)] struct GreaterThan10 {...

This sounds great! If I'm connecting a road at 45°, I can't think of a single time I've wanted the car to take the 135° corner -- especially not if...

> That would be fine with me. Wrapping `&Vec` and `&mut Vec` does not have the downsides that wrapping `Vec` itself does. This made me think. Anything that could possibly...

Note that `resize_default` was deemed unnecessary in https://github.com/rust-lang/rust/issues/41758#issuecomment-449719961 -- I think the same "just pass the function" may well apply here.

I raised the `const { CONST }` version on IRLO about two months back: https://internals.rust-lang.org/t/bring-enum-variants-in-scope-for-patterns/12104/51?u=scottmcm There are two interesting replies that suggest the extra noise from requiring the keyword in...

> are we going to have postfix `if`, `for` and `while` Here's my previous thoughts on this: https://internals.rust-lang.org/t/half-baked-idea-postfix-monadic-unsafe/10186/11?u=scottmcm Basically, Rust is pretty good about "there's a warning up front" when...

> Currently, the `match` expressions are minor sequence points, which require the code author to give some, hopefully descriptive, name to the state. This is a benefit of the standard...

We discussed this in the lang meeting today. The consensus was that since this is currently possible to be written using existing stable volatile things (https://github.com/rust-lang/rfcs/pull/2728/files#r305730848), that there's no lang...