Unable to find repo in ancestor path in non-existent parent path.

[hi-rustin]

Cargo uses this bind API to find the root repo when users call cargo new.
But we found that if it is unable to find repo in ancestor path in non-existent parent path.

For example:

1. init git in /User/rustin/test
2. try find the repo in /User/rustin/test/non-exist path.

See more at rust-lang/cargo#10981.

Also, you can check out rust-lang/cargo#10987 to see if you pass an existing path for it. It will work.

Please correct me if I have misunderstood the meaning of this API. Thank you!

[ethomson]

This is definitely by design. The goal of this api is to discover the root of the repo for your current working directory. (So that, eg, git add . works several levels down.)

Not necessarily opposed to adding an option here that the trailing paths may be imaginary. We could convert across_fs to flags with little impact on compatibility.

[hi-rustin]

Not necessarily opposed to adding an option here that the trailing paths may be imaginary. We could convert across_fs to flags with little impact on compatibility.

Thanks for your help!
Should I open a feature request issue or we can just convert this discussion to an issue?