Closed timotheecour closed 8 months ago
check = true
seems a bit problematic to me because you turn the check failure into an untracked AssertionError exception. However, it is better than a hypothetical proc rebasePath*(path, oldBase, newBase: string, check = true): string {.raises: ValueError.}
solution which then cannot really fail when you pass check = false
. But maybe that's an indication that we want two procs rather than one.This RFC is stale because it has been open for 1095 days with no activity. Contribute a fix or comment on the issue, or it will be closed in 30 days.
proposal
add this to std/os