Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@k3DW
Copy link
Contributor

@k3DW k3DW commented Mar 16, 2024

Closes #168

@pdimov
Copy link
Member

pdimov commented Mar 17, 2024

I don't think the GCC part is needed; we don't get any warnings from GCC.

@k3DW
Copy link
Contributor Author

k3DW commented Mar 17, 2024

I'll remove the GCC portion

@k3DW
Copy link
Contributor Author

k3DW commented Mar 17, 2024

Some of the drone GCC stages are showing failures with deprecated-declarations, so I'll add back the GCC portion, this time using BOOST_GCC

@k3DW k3DW force-pushed the feature/168 branch 2 times, most recently from 7e8ec31 to ecf10bf Compare March 17, 2024 05:54
@Lastique Lastique merged commit 083b41c into boostorg:develop Mar 19, 2024
@k3DW k3DW deleted the feature/168 branch June 19, 2024 01:42
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.

boost::allocator_destroy() emitting deprecated warnings for std::pmr::polymorphic_allocator in Clang 18.1.0 with C++20

3 participants