Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error_code_extended should stop misusing the boost-lite lightweight logger for storage #52

Closed
ned14 opened this issue May 30, 2017 · 1 comment

Comments

@ned14
Copy link
Owner

commented May 30, 2017

Options:

  • Could keep payload inline. This could significantly bloat the stack though.
  • Could use malloc. This loses trivial destruction though.
  • Could use a different static ringbuffer, perhaps with Peter's chaining idea. This retains the problem of storage suddenly vanishing due to another thread expiring storage.

Still to be decided:

  • Should we fix how std::error_code is not constexpr-capable and make this error code all-constexpr-capable? An alternative all-constexpr error_code implementation might be superior all round, but then we lose direct convertibility to std::error_code. Still, an explicit converting operator might make it acceptable.
@ned14 ned14 added the enhancement label May 30, 2017
@ned14

This comment has been minimized.

Copy link
Owner Author

commented Jul 8, 2017

Removed in v2

@ned14 ned14 closed this Jul 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.