We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is it interesting to add the management of the assertions in SARL and thus the assert keyword ?
Personnally I think it is interesting. But it is not mandatory to have a keyword, since we already have an access to assertTrue from JUnit
The text was updated successfully, but these errors were encountered:
But JUnit is a library that is dedicated to unit tests. It may be confusing to use a part of this API in a "standard" code.
If we decide to not introduce a keyword, I prefer to use the API given by Preconditions than the one from JUnit.
Sorry, something went wrong.
One more remark: if we do not introduce a keyword, it will be difficult to detect the cases of potential null values (as done by the Java compiler).
This work should be done at the same time as the one for the issue #9.
This issue is related to the Xtext bug 442320.
gallandarakhneorg
No branches or pull requests
Is it interesting to add the management of the assertions in SARL and thus the assert keyword ?
Personnally I think it is interesting. But it is not mandatory to have a keyword, since we already have an access to assertTrue from JUnit
The text was updated successfully, but these errors were encountered: