The problem I am trying to solve is the complexity of the current lifetime annotation, that makes everyone will just avoid it so Rust in reality is not like Rust in paper For example : struct DatabaseConfig<'a, 'b> { host: &'a str, query_cache: &'b [u8], } struct NetworkConfig<'c> { bind_address: &'c str, } struct Server<'a, 'b, 'c> { db: DatabaseConfig<'a, 'b>, net: NetworkConfig<'c>, } struct App<'a, 'b, 'c> { server: Server<'a, 'b, 'c>, } impl<'a, 'b, 'c> App<'a, 'b, 'c> { fn run(&self) { println!("{}", self.server.db.host); } } That code is scary and confusing, all the requirement 'a, 'b, 'c will keep spread to the other code that call them Then, it become like this : struct DatabaseConfig { host: &str, query_cache: &[u8], } struct NetworkConfig { bind_address: &str, } struct Server { db: DatabaseConfig, net: NetworkConfig, } struct App { server: Server, } impl App { fn run(&self) { println!("DB Host: {}", self.server.db.host); println!("Net Bind: {}", self.server.net.bind_address); } } // simulating the use of borrow fn main() { let host_data = String::from("localhost") until MyLifetime; let cache_data = vec![1, 2, 3] until MyLifetime; let bind_data = String::from("0.0.0.0") until MyLifetime; let app = App { server: Server { db: DatabaseConfig { host: &host_data, query_cache: &cache_data }, net: NetworkConfig { bind_address: &bind_data }, } } until MyLifetime; app.run(); close MyLifetime; } For the Thread at_exit hook, the problem it solves is the limitation of `std::thread::scope` that force to wait in place where it is written, with the cons can't use reference to stack data, but only using reference to heap data. It removes the usual need of Arc if want to share heap data to other 1 thread

Light

This article describes why a static route or default route outgoing with SD-WAN Zone cannot be assigned an administrative distance of 10 on a FortiGate.

A smart Flutter network package with built-in error handling, configurable retry, and multilingual error messages (en/ar). Changelog excerpt: ### Features - **Configurable retry**— `NetworkConfig`now accepts a `retry`policy. `RetryPolicy`exposes `attempts`, `delays`, `methods`and `statuses`, all of which were previously hardcoded. Pass `retry: null`to disable retry app-wide. - **Per-request retry**— `request()`, `download()`and `uploadFile()`take a `retry:`argument that overrides the app-wide policy for a single call. Use `RetryPolicy.off`to opt one request out, or a policy with a higher `attempts`to opt one in. - **New public export[...]

This article describes that it is not possible to set the negotiation option for the WAN interface to manual. The option only shows ‘Auto’ Scope FortiGate

Hi, i have a problem where i don't know what to do. Its a virtual server at Hetzner. They announced to change the "network model". To do this i should change networkconfig to DHCP, poweroff server, update "network model", power on server. It allready was on DHCP so i only did the "network model". But now it won't boot. I have console access. It says: Booting from Hard Disk... /boot/config: (smiley symbol?) FreeBSD/x86 boot Default: zroot/ROOT/.... boot: / Can't fint (smiley symbol) I feel overwhelmed with this. What should i do?