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.
What other cool stuff can "management, strategy, and customer satisfaction cadres" even do? And if just because "management, strategy, and customer satisfaction cadres" is not doing "supercool stuff" (whatever it means), the company should focus on R&D, then the vast majority of companies should cease to exist. Like it or not, companies are here to make money.
Saying MS should reinvent itself to be a R&D company is like saying Toyota should stop making cars because their normal cars aren't running by water, auto driven, and charged by solar panels yet. Ya, what's the point? Use your money to research on energy, AI and what not. Never mind where that money comes from.
When I read these absurd statements I think the author is either trolling, has an agenda, or is living in a bubble.
Is the currying example even currying? It looks like it's just a function returning a function to me. I thought currying it's some thing like func contains(subString: String, string: String) -> Bool, and calling contains("a") would automatically return a func(x: String) -> Bool.
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.