You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
23 lines
1.1 KiB
23 lines
1.1 KiB
3 years ago
|
---
|
||
|
title: "Impurity"
|
||
|
description: "Detects functions with potential side-effects. Same as \"purity\", but implemented on top of Pulse."
|
||
|
---
|
||
|
|
||
|
Detects functions with potential side-effects. Same as "purity", but implemented on top of Pulse.
|
||
|
|
||
|
Activate with `--impurity`.
|
||
|
|
||
|
Supported languages:
|
||
|
- C/C++/ObjC: Experimental
|
||
|
- Java: Experimental
|
||
|
- C#/.Net: Experimental
|
||
|
|
||
|
This is an experimental inter-procedural analysis that detects impure functions. It is meant to be an improvement over the [purity](/docs/checker-purity) analysis with a negation on the issue types. For each function, impurity analysis keeps track of not only the impurity of the function but also some additional information such as which parameters/globals the function modifies. It models functions with no summary/model as impure. The analysis relies on [Pulse](/docs/checker-pulse) summaries to determine impurity.
|
||
|
|
||
|
|
||
|
## List of Issue Types
|
||
|
|
||
|
The following issue types are reported by this checker:
|
||
|
- [IMPURE_FUNCTION](/docs/all-issue-types#impure_function)
|
||
|
- [MODIFIES_IMMUTABLE](/docs/all-issue-types#modifies_immutable)
|