-
Notifications
You must be signed in to change notification settings - Fork 42
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
S4 class-based extension mechanism #256
Comments
I am not yet sure whether we want to use S4 or S3. Even though
|
@SamikDatta has just illustrated to me in an email why we need to use method dispatch for the mizer extension mechanism: currently two expansion packages that define their own rate functions which in turn utilise the mizer rate functions do not compose. The example Samik gives is therMizer not working together with mizerMR |
Make functions that extension packages may want to change into methods. This includes all functions whose first argument is either a MizerParams or a MizerSim object. Extension packages would then create subclasses of these classes to dispatch their own methods.
The text was updated successfully, but these errors were encountered: