@grainloom You'd definitely build the switches and routers. Maybe spawn the world with a fixed "gateway" block and you have to implement your own switches and routers around it. Then you can implement BGP to, well, do what BGP does, really. routing and stuff.
@grainloom Maybe with BGP.
@grainloom Yeah, I too wish every OC computer could get its own public IPv6 address and connect to a central in-game router through multiple layers of switches and routers.
@grainloom I'm saying "to hell with OC it's not good enough".
I may have too high standards... but I really really wish it had at least a distributed package manager.
@grainloom It's OC, you can't do git (no RTC/NTP for commit time), TLS (no RTC/NTP for cert validation), or distributed/serverless package managers (OPPM uses github as its server).
@grainloom That's a con?
@grainloom @eden I'll make all my crates define commonly used lowercase identifiers as constants in literally every module.
Rust should not be context-sensitive.
@grainloom @eden _ is not an identifier.
@grainloom @eden Yes, removal is backwards-incompatible. But that's only removal.
most of my 1525 posts are just "- - -" and they're DMs
@grainloom @eden yes, that's the idea, but also how do you keep it from breaking old code?
@grainloom @eden I don't understand what you just said.
@grainloom @eden Say that when dependency X of dependency Y stops compiling, stopping you from developing your crate unless you manually edit Cargo.lock.
Remember to add weird all-lowercase const symbols between patch releases of your #Rust crates. (like "pub const x: u32 = 0" or "pub const pos: u32 = 0")
Even if there's absolutely no reason to add them. Even if their whole purpose is to do nothing.
Add them *especially* when they're relevant for a bug fix (forgot to add a case for something that's equivalent to something else, add a const for the case and then add the case).
@grainloom @eden Yes, and it's just a warning.
@grainloom @eden "my original one"? I literally tested the examples without `use` in patterns, and they all compile.
Reminder that if you're doing #rust dev work you should always commit Cargo.lock regardless of if you're a library or a binary.
Considering something I learned recently, this cannot be called bad advice, even if it usually is called bad advice.
I'm so done with rust. >.<
@grainloom / is too useful.