diff options
| author |  ridiculousfish <corydoras@ridiculousfish.com> | 2014-11-09 22:02:46 -0800 |
|---|---|---|
| committer | ridiculousfish <corydoras@ridiculousfish.com> | 2014-11-09 22:03:04 -0800 |
| commit | 338a1311f58208b582ddc80ff33acbbffec38767 (patch) | |
| tree | 2309fd8a39b4c8081f5f69f267c3569c68aa9213 /env_universal_common.cpp | |
| parent | 00e0ed64bc2e4b918357b10fbd176797eeb07402 (diff) | |
Make a string into a reference, to save a copy
Diffstat (limited to 'env_universal_common.cpp')
| -rw-r--r-- | env_universal_common.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/env_universal_common.cpp b/env_universal_common.cpp index e57fe9b8..f4516504 100644 --- a/env_universal_common.cpp +++ b/env_universal_common.cpp @@ -718,7 +718,7 @@ bool env_universal_t::sync(callback_data_list_t *callbacks) Prior versions of fish used a hard link scheme to support file locking on lockless NFS. The risk here is that if the process crashes or is killed while holding the lock, future instances of fish will not be able to obtain it. This seems to be a greater risk than that of data loss on lockless NFS. Users who put their home directory on lockless NFS are playing with fire anyways. */ - const wcstring vars_path = explicit_vars_path.empty() ? default_vars_path() : explicit_vars_path; + const wcstring &vars_path = explicit_vars_path.empty() ? default_vars_path() : explicit_vars_path; /* If we have no changes, just load */ if (modified.empty()) |