let lines = {
let ret = vec![];
// Open file
// Read into ret
ret
};
let processed_data = {
// Open another file
// Use lines
// Construct ret
ret
};
....
You get the best of both worlds this way: scoped, meaningful names like with sub-functions and the continuity of a long one.
Everything is an expression is an underrated feature of Rust.
They implemented what looks like the Rust ownership model: SE-0176 Enforce Exclusive Access to Memory (https://github.com/apple/swift-evolution/blob/master/proposa...), but I'm having a hard time understanding the proposal, can anyone shed some light on this?
I dislike the rigidity of the original pomodoro technique, so I made a flexible one without the fixed time slots. You only have a minimum working duration, work for however long you like. I found that way it doesn't break my flow.
Hey I'm working on a side project, looking to grow it and would love to talk with someone who have done it before. However I couldn't find any contact information in your profile.
You get the best of both worlds this way: scoped, meaningful names like with sub-functions and the continuity of a long one.
Everything is an expression is an underrated feature of Rust.