Skip to content

Conversation

@arximboldi
Copy link
Owner

More details in the individual commits.

Ping @aimoonchen @alex-sparus

The fix involves preferring () to {} when calling placement-new generally,
as the latter often leads to the initialization_list based constructor
to be preferred, which causes the issue.

This was introduced in:
6d22844
This reintroduces the check that was removed in:
6d22844

It does so in a way that is compatible with incomplete types.
They are pseudo-deterministically flaky? Depends on when GC gets
triggered...  Seems mostly deterministic for a single buidl, but the
points change whenever you really change the code in any way.
@arximboldi arximboldi merged commit 6adf650 into master Jan 13, 2026
81 checks passed
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.

2 participants