Yuya Nishihara da221eb888 repo: load index eagerly to simplify error handling ... If readonly_index() and index() returned Result, it would propagate to many call sites. That seems bad for API ergonomics. Suppose most "repo" commands depend on an index, I think it's okay to load index eagerly: - "jj config" doesn't load repo (nor index) - "jj workspace root" doesn't load repo (nor index) - some other mutation commands load index when printing commit summary - many other commands load index when resolving revset		2024-07-23 18:26:16 +09:00
..
benches	cargo: rename crates from jujutsu/jujutsu-lib to jj-cli/jj-lib	2023-07-09 06:40:43 +02:00
gen-protos	Use { workspace = true } to appease VS Code's Cargo.toml parser	2023-08-22 21:38:53 -07:00
proc-macros	cargo: explicitly indicate paths to publish	2024-04-15 20:37:00 -07:00
src	repo: load index eagerly to simplify error handling	2024-07-23 18:26:16 +09:00
tests	str_util: add regex pattern	2024-07-22 12:00:52 +09:00
testutils	copy-tracking: stub get_copy_records	2024-07-03 20:26:30 -04:00
Cargo.toml	cargo: add "bstr" dependency	2024-07-14 23:26:29 +09:00
LICENSE	cargo: add LICENSE file to each crate we publish	2023-09-22 21:48:28 -07:00