summaryrefslogtreecommitdiffstats
path: root/lldb/scripts/Python
diff options
context:
space:
mode:
authorRafael Espindola <rafael.espindola@gmail.com>2013-11-05 23:41:57 +0000
committerRafael Espindola <rafael.espindola@gmail.com>2013-11-05 23:41:57 +0000
commit03cb49e15985dcbf8122fd49af14ed9bf9169cd4 (patch)
tree52f1c0d3a5b104efc43244ecf1d01fceaff8276a /lldb/scripts/Python
parent7ded5b6ab9f6e60cb57a59045e8dc5408acadbce (diff)
downloadbcm5719-llvm-03cb49e15985dcbf8122fd49af14ed9bf9169cd4.tar.gz
bcm5719-llvm-03cb49e15985dcbf8122fd49af14ed9bf9169cd4.zip
Remove another unused, and IMHO, not very desirable feature of ErrorOr.
One of the uses of the IsValid flag is to support default constructing a ErrorOr that is not a Error or a Value. There is not much value in doing that IMHO. If ErrorOr was to have a default constructor, it should be implemented by default constructing the value, but even that looks unnecessary. The other use is to avoid calling destructors on moved objects. This looks wrong. If the data being moved has non trivial treatment of moves (an std::vector for example), it is its destructor that should handle it, not ~ErrorOr. With this change ErrorOr becomes a fairly simple wrapper and should always be better than using an error_code + value in an API. llvm-svn: 194109
Diffstat (limited to 'lldb/scripts/Python')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud