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

new(...) vs __new(...) #3

Open
skrolikowski opened this issue Jun 20, 2019 · 0 comments
Open

new(...) vs __new(...) #3

skrolikowski opened this issue Jun 20, 2019 · 0 comments
Labels
enhancement 👍 New feature or request idea 💡 Proposed idea.. may be included.
Milestone

Comments

@skrolikowski
Copy link
Owner

💡 Idea:

Problem:
When calling a "new" Module, the new(...) functions will be called. If the Module includes Mixins, then their new(...) functions will be called as well. For some, this may not be acceptable, due to the Mixins requiring a different set of arguments.

Solution:
Introduce a new function __new(...), which will override a Mixin's new(...) call if one exists, otherwise fallback to the default new(...) function.

@skrolikowski skrolikowski added enhancement 👍 New feature or request idea 💡 Proposed idea.. may be included. labels Jun 20, 2019
@skrolikowski skrolikowski added this to the 0.2-1 milestone Jun 20, 2019
@skrolikowski skrolikowski self-assigned this Jun 20, 2019
@skrolikowski skrolikowski modified the milestones: 0.2-1, 0.3-1 Jun 26, 2019
@skrolikowski skrolikowski removed their assignment Jun 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement 👍 New feature or request idea 💡 Proposed idea.. may be included.
Projects
None yet
Development

No branches or pull requests

1 participant