rust-lang / rfcs

RFCs for changes to Rust
https://rust-lang.github.io/rfcs/
Apache License 2.0
5.96k stars 1.57k forks source link

Closure-level inline constants #3687

Open sojuz151 opened 2 months ago

sojuz151 commented 2 months ago

I propose to add closure-level inline constants. For example the following code

let closeure_uuid = Uuid::new_v4();
let lambda = ||  {
println!("Execution UUID {}",Uuid::new_v4());
println!("Closure UUID {}",closeure_uuid);
};
lambda ();
lambda ();

It could be rewritten as

let lambda = ||  {
println!("Execution UUID {}",Uuid::new_v4());
println!("Closure UUID {}",cc{Uuid::new_v4())});
};
lambda ();
lambda ();

with a new cc keyword similar to constant. This would have similar advantages as inline_const https://github.com/rust-lang/rust/pull/104087. Use cases:

Finer control on what is getting moved inside the lambda. For example

cc{very_larnge_vector.iter().min()}

or

cc{struct.field.other_filed}

More ergonomic dealing with ref counting. Example:

cc{button.clone()}.enable();

Those expressions should be executed when the closure is created and dropped when the closure is dropped.

workingjubilee commented 1 month ago

I don't understand the proposal tbh, is this just an abbreviated syntax for const {}?

kennytm commented 1 month ago

this is like one of the capturing alternatives proposed in https://github.com/rust-lang/rfcs/pull/3680#issuecomment-2308559508.

as explained in https://github.com/rust-lang/rfcs/pull/3680#issuecomment-2328377258 it is very hard to grasp the scope/lifetime of the cc {}'ed expression for newcomers.

workingjubilee commented 1 month ago

ah, I see. thank you.