This assures that we don't overwrite a random file called wallet.backup that happens to be in the current directory. It also assures that the temporary file will be cleaned up.
Noticed by Evan Klitzke, came up in discussion here: #10880 (review)
This assures that we don't overwrite a random file called wallet.backup that happens to be in the current directory. It also assures that the temporary file will be cleaned up.
Noticed by Evan Klitzke, came up in discussion here: #10880 (review)
This assures that we don't overwrite a random file called
`wallet.backup` that happens to be in the current directory. It also
assures that the temporary file will be cleaned up.
Noticed by Evan Klitzke, came up in discussion here:
https://github.com/bitcoin/bitcoin/pull/10880#discussion_r128460722
utACK 88af2276876868fc5b17a67ecaa86b219969d4c6
utACK 88af227.
utACK 88af2276876868fc5b17a67ecaa86b219969d4c6
Excerpt from the boost::filesystem::path documentation for some context:
The append operations use
operator/=to denote their semantic effect of appending the platform's preferred directory separator when needed.
utACK
Thanks! utACK 88af2276876868fc5b17a67ecaa86b219969d4c6