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

Use std::launder for pointers to placement-new constructed objects #1570

Closed
wants to merge 1 commit into from

Conversation

djarek
Copy link
Contributor

@djarek djarek commented Apr 13, 2019

std::launder must be used whenever placement-new of an unknown type is performed and the result of the placement-new expression is discarded.

`std::launder` must be used whenever placement-new of an unknown type
is performed and the result of the placement-new expression is discarded.

Signed-off-by: Damian Jarek <damian.jarek93@gmail.com>
@codecov
Copy link

codecov bot commented Apr 13, 2019

Codecov Report

Merging #1570 into develop will increase coverage by <.01%.
The diff coverage is 100%.

Impacted file tree graph

@@             Coverage Diff             @@
##           develop    #1570      +/-   ##
===========================================
+ Coverage    92.61%   92.61%   +<.01%     
===========================================
  Files          150      151       +1     
  Lines        12102    12106       +4     
===========================================
+ Hits         11208    11212       +4     
  Misses         894      894
Impacted Files Coverage Δ
include/boost/beast/websocket/detail/decorator.hpp 91.35% <100%> (+0.21%) ⬆️
include/boost/beast/core/detail/type_traits.hpp 100% <100%> (ø)
include/boost/beast/core/detail/variant.hpp 100% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0345aa1...47b4549. Read the comment docs.

@djarek djarek deleted the cxx17_launder branch September 10, 2019 21:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant