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

If a parameter is required but provides a default value, use the default value lower bound as the parameter lower bound #176

Open
abstratt opened this issue Nov 27, 2019 · 0 comments

Comments

@abstratt
Copy link
Owner

For instance, in the signature below, clients should be able to omit a value for date, and the implementation of newCharge should still be able to rely on it not being null.

    static operation newCharge(taxi : Taxi, payer : Driver, date : Date := { Date#today() });

We either need to relax the verification on the operation call site, or allow the modeler the declare the parameter as optional and still consider it to be required in the body of the operation implementation.

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

No branches or pull requests

1 participant