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

Don't use copy constructors, as they will cause a stackoverflow #43

Merged
merged 1 commit into from
Feb 21, 2024

Conversation

tknell
Copy link
Member

@tknell tknell commented Feb 21, 2024

  • As the Beanfiller defaults to the same constructor each time, it tries to create another object with the same copy constructor until the program reaches a stackoverflow
  • Copy constructors (more specifically constructors with the same object that should be created as parameter) will no longer be used
  • When the only available constructor is a copy constructor, there will now be an exception that another constructor must be provided

* As the Beanfiller defaults to the same constructor each time,
  it tries to create another object with the same copy constructor
  until the program reaches a stackoverflow
* Copy constructors (more specifically constructors with the same object
  that should be created as parameter) will no longer be used
* When the only available constructor is a copy constructor, there
  will now be an exception that another constructor must be provided
@tknell tknell merged commit ded38d9 into master Feb 21, 2024
2 checks passed
@tknell tknell deleted the dont-use-copy-constructors branch February 21, 2024 10:36
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.

1 participant