#[debug_visualizer] seems like it will be very useful.

One of the current issues with Rust (and a place where C++ is still better) is debugging. Granted, I end up needing to debug Rust code much less often than C++ code, but it would still be nice to actually call rust functions in IntelliJ (and it seems there's limited support in gdb and lldb), and view data-structures like maps opaquely instead of just their complex internals.

From cargo's changelog [0]

> Automatically inherit workspace fields when running `cargo new`/`cargo init`. #12069 [1]

imo I think this is a big quality of life improvement

[0] https://github.com/rust-lang/cargo/blob/master/CHANGELOG.md#...

[1] https://github.com/rust-lang/cargo/pull/12069

Debugger visualization is a really great idea. I hadn’t thought of using attribute annotation to do it but now I’m wishing more languages had that.

Nice to have the option to unwind across an FFI boundary. It's also good that (in a future release) erroneously unwinding across a C ABI boundary will abort, instead of being undefined behaviour.

I'm excited about the array <-> tuple conversion! (At least for small ones.)

vendor/regex-syntax, vendor/regex-syntax-0.6.26, vendor/regex-syntax-0.6.28, vendor/regex-syntax-0.6.29

vendor/cargo_metadata, vendor/cargo_metadata-0.14.0, vendor/cargo_metadata-0.14.2, vendor/cargo_metadata-0.15.2

vendor/filetime, vendor/filetime-0.2.16, vendor/filetime-0.2.19, vendor/filetime-0.2.20

vendor/parking_lot_core, vendor/parking_lot_core-0.8.5, vendor/parking_lot_core-0.8.6, vendor/parking_lot_core-0.9.4, vendor/parking_lot_core-0.9.6

etc. Lovely.

I write billing apps because I'm a masochist and feel there is deeper meaning to be gained through suffering. Lot of data and rules to process. Torn between learning Go or Rust next.

I think versioning like 13.07.23 is better.

You automatically get:

- Minor version upgrade every day.

- Major version upgrade every month.