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

Fix special functions order #312

Open
sebalaig opened this issue Apr 9, 2021 · 0 comments · May be fixed by #311
Open

Fix special functions order #312

sebalaig opened this issue Apr 9, 2021 · 0 comments · May be fixed by #311

Comments

@sebalaig
Copy link
Contributor

sebalaig commented Apr 9, 2021

  • Do you want to request a feature or report a bug?
    Code cleanup

  • What is the current behavior?
    In code, special functions are often written in the following order :

  • Constructor
  • Destructor
  • Copy constructor
  • Move constructor
  • Copy assignment operator
  • Move assignment operator
  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
    No

  • What is the expected behavior?
    Special function should be in the following order:

  • Constructor
  • Copy constructor
  • Move constructor
  • Destructor
  • Copy assignment operator
  • Move assignment operator
  • What is the motivation / use case for changing the behavior?
    Cleanup

  • Please tell us about your environment:

    • PowSyBl Version: ...
    • OS Version: ...
  • Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, spectrum, etc)

(if a question doesn't apply, you can delete it)

@sebalaig sebalaig linked a pull request Apr 9, 2021 that will close this issue
5 tasks
@sebalaig sebalaig linked a pull request Apr 9, 2021 that will close this issue
5 tasks
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 a pull request may close this issue.

1 participant