1a20c557b8
Summary: The documentation includes `std` exceptions like `std::bad_alloc` or `std::system_error`, for which there's probably nothing we can do. This may seem unnecessary, but it will be really helpful when writing the C API for interfacing with custom modules and plugins, as well as when switching to storage v2 API. In general, we should start updating the documentation of functions which may throw exceptions. This ought to be enforced in code review, so that the implementation and documentation are kept in sync. Reviewers: mferencevic, mtomic, msantl Reviewed By: mferencevic Subscribers: pullbot Differential Revision: https://phabricator.memgraph.io/D2288 |
||
---|---|---|
.. | ||
audit | ||
auth | ||
communication | ||
data_structures | ||
database | ||
durability | ||
glue | ||
integrations | ||
io | ||
lisp | ||
query | ||
raft | ||
requests | ||
slk | ||
stats | ||
storage | ||
telemetry | ||
transactions | ||
utils | ||
CMakeLists.txt | ||
config.hpp | ||
memgraph_ha.cpp | ||
memgraph_init.cpp | ||
memgraph_init.hpp | ||
memgraph.cpp | ||
version.hpp.in |