; but we can still provide a symbolic [de]serialization for specifically <a class="el" href="namespaceipc_1_1transport_1_1error.html#adfef15ef4e76cc55d652fbd9c2797297" title="All possible errors returned (via Error_code arguments) by ipc::transport functions/methods outside o...">transport::error::Code</a>. Why did we want that? Answer: The original use case was in testing scenarios, to easily specify an expected outcome of an <a class="el" href="namespaceipc_1_1transport.html" title="Flow-IPC module provid