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

Remove destructors #18

Merged
merged 1 commit into from
Dec 7, 2018
Merged

Remove destructors #18

merged 1 commit into from
Dec 7, 2018

Conversation

oprypin
Copy link
Owner

@oprypin oprypin commented Dec 6, 2018

@dom96 what do you think?

@dom96
Copy link
Contributor

dom96 commented Dec 7, 2018

Might be worth waiting for the new Nim destructors to stabilise, it is a feature that is being worked on pretty heavily so hopefully it will be ready soon. This library could be a brilliant showcase for it so it would be a shame to remove all the destructors.

@oprypin
Copy link
Owner Author

oprypin commented Dec 7, 2018

The reason I'm thinking about this is I want to make a release with sfml 2.3, then with sfml 2.4, then with sfml 2.5!
And I don't want all of them to be broken by default.

Re-adding this would not be that big of a problem.

@dom96
Copy link
Contributor

dom96 commented Dec 7, 2018

okay, go for it then

@oprypin oprypin merged commit fa756bd into master Dec 7, 2018
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