Sure, in areas without robust transit, transit is a problem. But I'm responding to RandallBrown's assertion that there's a persistent last mile issue in areas with robust transit. There's not. Manhattan is evidence that robust transit solves the last mile problem for most people.
> Trains still don't solve last mile transport for most people
This has not been my experience since moving to Manhattan last January. Subways, alone, close the gap between regional rail and most destinations astoundingly well. I haven't yet needed to use a bus (but they seem abundant, too), and I haven't even thought of taking a taxi yet.
Here, robust transit has solved the last mile problem for most people.
> The Clamzorians are animists. They believe every rock and tree and river has its own spirit. And those spirits are legal people. This on its own is not unusual – even New Zealand gives rivers legal personhood. But in Clamzoria, if a flood destroys your home, you sue the river.
I don't think that having two numbers will help much. I'd guess that most sim-swapped cell numbers are leaked in data breaches or acquired through data brokering. Enrolling a number in 2fa is letting people know your number, because you're tying that number to the account.
A separate number for each account might help. Maybe.
It's an area of active development! I'm hopeful the situation will improve significantly this year.
For tracing suspended Futures, I've worked on a few approaches:
1. If you don't mind annotating your async functions, you can use the async-backtrace crate, which provides pretty-printing out-of-the-box: https://crates.io/crates/async-backtrace
2. If you are already using the `tracing` ecosystem, you can use the tracing-causality crate (it doesn't yet include pretty-printing, but it's not too hard to add that on): https://crates.io/crates/tracing-causality
I fantasize about that, too. You might be interested in the work of Culdesac (https://culdesac.com/); they're building an expressly car-free neighborhood, from scratch.
I'm optimistic that I can make strides closer to home. I have only ever lived in places that predated the advent of automobiles. At one time, they were very accessible via walking, biking, rail, and trolley. So, last fall, when I moved back to Providence, I made it my mission to get involved in local transit activism. It's been a great source of social and civic satisfaction, and I intend to repeat the exercise when I move again next Fall.
It feels like positive change is (slowly) happening.
It only works if DWARF is generated. By default, the `release` profile of Cargo sets `debug = false` [0]. But, it's quite easy to override this setting, and have a build that is both optimized and includes debuginfo.
Absolutely! That's the approach that frunk [0] takes. Frunk (and other reflection libraries like it) are suitable for most use cases, and make better use of Rust's affordances.
My crate is suitable for cases where you cannot know (or control) the set of types you might need to reflect on in advance. It's primary use-cases are related to debugging.
Yes, unfortunately that's a tradeoff here. Rust does support splitting debug info into other files, but Deflect doesn't support loading split debuginfo yet.
> Also note that you have to go out of your way to get broken by such additions: you have to declare a trait, then implement that trait for a group of types that you didn't define, and then use that trait on standard library types.
I also think you might be downplaying the ease of hitting of the problem, too. While RFC1105 declares that this sort of breakage is acceptable, Rust's maintainers are, in practice, (understandably) hesitant to break builds. The stabilization of `Iterator::intersperse` was aborted after it was discovered that doing so would break the no-less-than 319 crates that directly or transitively depend on `Itertools::intersperse`: https://github.com/rust-lang/rust/pull/89638
Speaking as one of the maintainers of itertools: This whole situation feels kinda awful, and kinda makes me want to discourage others from using itertools. :(
We've made a point to ride all the lines, but mostly ride Red Line (with a dash of Green), plus the Providence commuter rail line. Our rides tend to be during evenings, so the cars aren't sparkling clean. But, so far, the worst we've experienced are some loose french fries.
1) Amtrak isn't light rail. It definitely doesn't smell like piss.
2) Your characterization of light rail does not remotely resemble the reality my partner and I have experienced in the Boston area. We have yet to ride in a rail car that "smells like piss". It's fast, safe, and inexpensive. We do not have to worry about enduring property damage to our private vehicles, or injury from other drivers. I suspect our experience is not unusual among MBTA riders; per the 2015-17 MBTA Systemwide Passenger Survey [1], 70% of subway riders have access to one or more cars and 82% hold a valid drivers license.