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

Default constructor value behavior change #79

Open
pemessier opened this issue Apr 22, 2022 · 0 comments
Open

Default constructor value behavior change #79

pemessier opened this issue Apr 22, 2022 · 0 comments

Comments

@pemessier
Copy link
Contributor

Since 5f17234 from @knatten , there is a behavior change as well, the underlying type initial value is not the same as before. For example, a POD like int or double would be initialized to 0 before this changeset which could be handy. Now it behaves like a POD by leaving the memory as-is, which is also correct. However this is a big behavior change.

Is there a way we could force the old behavior (prehaps using a new skill)?

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

No branches or pull requests

1 participant