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
This issue has been migrated from Redmine: https://dev.icinga.com/issues/10760
Created by tgelf on 2015-12-01 15:40:22 +00:00
Assignee: gbeutner Status: Resolved (closed on 2015-12-01 15:41:39 +00:00) Target Version: 2.4.2 Last Update: 2015-12-08 14:38:43 +00:00 (in Redmine)
Icinga Version: 2.4.1 Backport?: Already backported Include in Changelog: 1
It happened to me to define
a = { name => value }
instead of
a = { name = value }
In this case I'd like to see an error message as follows:
<3> => d = { 3 } ^ Value computed is not used.
Cheers, Thomas
Changesets
2015-12-01 15:41:00 +00:00 by (unknown) 678a237
Turn '=>' lambda expressions into side-effect-free statements fixes #10760
2015-12-08 14:31:09 +00:00 by (unknown) f3ea00b
The text was updated successfully, but these errors were encountered:
Updated by gbeutner on 2015-12-01 15:40:52 +00:00
Sorry, something went wrong.
Updated by Anonymous on 2015-12-01 15:41:39 +00:00
Applied in changeset 678a237.
Updated by mfriedrich on 2015-12-08 14:31:26 +00:00
Updated by mfriedrich on 2015-12-08 14:38:43 +00:00
No branches or pull requests
This issue has been migrated from Redmine: https://dev.icinga.com/issues/10760
Created by tgelf on 2015-12-01 15:40:22 +00:00
Assignee: gbeutner
Status: Resolved (closed on 2015-12-01 15:41:39 +00:00)
Target Version: 2.4.2
Last Update: 2015-12-08 14:38:43 +00:00 (in Redmine)
It happened to me to define
instead of
In this case I'd like to see an error message as follows:
Cheers,
Thomas
Changesets
2015-12-01 15:41:00 +00:00 by (unknown) 678a237
2015-12-08 14:31:09 +00:00 by (unknown) f3ea00b
The text was updated successfully, but these errors were encountered: