diff options
| author | Simon Marchi <simon.marchi@polymtl.ca> | 2022-01-24 20:00:46 -0500 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@polymtl.ca> | 2022-01-26 10:01:40 -0500 |
| commit | 5d10a2041eb843fd321ce1d850cf3e0df7648bc7 (patch) | |
| tree | a1bd00ecbd780dc194da8d44b713b09f10446c0a /gdb/compile | |
| parent | b583c328e71369f90f4042ac7973ce9edfdb44b3 (diff) | |
| download | fsf-binutils-gdb-5d10a2041eb843fd321ce1d850cf3e0df7648bc7.zip fsf-binutils-gdb-5d10a2041eb843fd321ce1d850cf3e0df7648bc7.tar.gz fsf-binutils-gdb-5d10a2041eb843fd321ce1d850cf3e0df7648bc7.tar.bz2 | |
gdb: add string_file::release method
A common pattern for string_file is to want to move out the internal
string buffer, because it is the result of the computation that we want
to return. It is the reason why string_file::string returns a non-const
reference, as explained in the comment. I think it would make sense to
have a dedicated method for that instead and make string_file::string
return a const reference.
This allows removing the explicit std::move in the typical case. Note
that compile_program::compute was missing a move, meaning that the
resulting string was copied. With the new version, it's not possible to
forget to move.
Change-Id: Ieaefa35b73daa7930b2f3a26988b6e3b4121bb79
Diffstat (limited to 'gdb/compile')
| -rw-r--r-- | gdb/compile/compile-c-support.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/compile/compile-c-support.c b/gdb/compile/compile-c-support.c index dd0dc91..4d9abfb 100644 --- a/gdb/compile/compile-c-support.c +++ b/gdb/compile/compile-c-support.c @@ -635,7 +635,7 @@ public: PopUserExpressionPolicy::pop_user_expression (&buf); AddCodeFooterPolicy::add_code_footer (m_instance->scope (), &buf); - return buf.string (); + return buf.release (); } private: |