Commit 1d50656
committed
but-hunk-assignment: clarify return value of
As documented, this function seems to perform an operation based on
the worktree changes and locks, but if the operation fails, falls
back to using the worktree changes alone, implying that the operation
may fail due to the locks. However, the only fallible part of the
operation (`reconcile_with_worktree_and_locks`) is I/O error on
`virtual_branches.toml` or database access.
Falling back on I/O or database error doesn't seem like a good idea - it
seems best to fail immediately.
Therefore, remove this fallback.
TODO: if we have a better name for `assignments_with_fallback`, we
should inline `reconcile_worktree_changes_with_worktree_and_locks` and
update all callers with the new name and signature before merging this
commit.assignments_with_fallback
1 parent ac86c81 commit 1d50656
1 file changed
+20
-9
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
319 | 319 | | |
320 | 320 | | |
321 | 321 | | |
322 | | - | |
323 | | - | |
324 | | - | |
325 | | - | |
| 322 | + | |
| 323 | + | |
326 | 324 | | |
327 | 325 | | |
328 | 326 | | |
329 | 327 | | |
330 | 328 | | |
331 | 329 | | |
| 330 | + | |
| 331 | + | |
| 332 | + | |
| 333 | + | |
| 334 | + | |
| 335 | + | |
| 336 | + | |
| 337 | + | |
| 338 | + | |
| 339 | + | |
| 340 | + | |
| 341 | + | |
| 342 | + | |
| 343 | + | |
| 344 | + | |
332 | 345 | | |
333 | 346 | | |
334 | 347 | | |
| |||
344 | 357 | | |
345 | 358 | | |
346 | 359 | | |
347 | | - | |
| 360 | + | |
348 | 361 | | |
349 | 362 | | |
350 | 363 | | |
| |||
360 | 373 | | |
361 | 374 | | |
362 | 375 | | |
363 | | - | |
364 | | - | |
365 | | - | |
| 376 | + | |
366 | 377 | | |
367 | 378 | | |
368 | | - | |
| 379 | + | |
369 | 380 | | |
370 | 381 | | |
371 | 382 | | |
| |||
0 commit comments