You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
### Summary of Changes
Remove the option to mark callable parameters as `@Pure`, since it could
collide with the impurity reasons on the containing function in various
ways. Now only the context decides, whether a callable parameter only
accepts pure callables or may be potentially impure.
"The purity of a callable parameter must be specified. Call the annotation '@Pure' or add the impurity reason 'PotentiallyImpureParameterCall' to the containing function.",
Copy file name to clipboardExpand all lines: packages/safe-ds-lang/tests/resources/validation/purity/callable parameter with unspecified purity/class.sdstest
Copy file name to clipboardExpand all lines: packages/safe-ds-lang/tests/resources/validation/purity/callable parameter with unspecified purity/function.sdstest
Copy file name to clipboardExpand all lines: packages/safe-ds-lang/tests/resources/validation/purity/pure and potentially impure callable parameter/main.sdstest
Copy file name to clipboardExpand all lines: packages/safe-ds-lang/tests/resources/validation/purity/pure parameter must have callable type/main.sdstest
Copy file name to clipboardExpand all lines: packages/safe-ds-lang/tests/resources/validation/style/unnecessary pure annotation call on pure function parameter/info.sdstest
0 commit comments