Skip to content

Control flow: return and raise #17121

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

Merged
merged 4 commits into from
Apr 3, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions crates/ruff_linter/resources/test/fixtures/pylint/unreachable.py
Original file line number Diff line number Diff line change
Expand Up @@ -12,3 +12,19 @@ class C:
del c
def foo():
return

def after_return():
return 1
print("unreachable")
print("and this")

def after_raise():
raise ValueError
print("unreachable")
print("and this")

def multiple_returns():
return 1
print("unreachable")
return 2
print("unreachable range should include above return")
25 changes: 15 additions & 10 deletions crates/ruff_linter/src/rules/pylint/rules/unreachable.rs
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ use std::collections::HashSet;
use itertools::Itertools;
use ruff_python_ast::{Identifier, Stmt};
use ruff_python_semantic::cfg::graph::{build_cfg, BlockId, Condition, ControlFlowGraph};
use ruff_text_size::{Ranged, TextRange};
use ruff_text_size::TextRange;

use ruff_diagnostics::{Diagnostic, Violation};
use ruff_macros::{derive_message_formats, ViolationMetadata};
Expand Down Expand Up @@ -46,19 +46,24 @@ pub(crate) fn in_function(checker: &Checker, name: &Identifier, body: &[Stmt]) {
let cfg = build_cfg(body);
let reachable = reachable(&cfg);

let mut unreachable = (0..cfg.num_blocks())
let mut blocks = (0..cfg.num_blocks())
.map(BlockId::from_usize)
.filter(|block| !reachable.contains(block) && !cfg.stmts(*block).is_empty())
.map(|block| cfg.range(block))
.sorted_by_key(ruff_text_size::Ranged::start)
.filter(|block| !cfg.stmts(*block).is_empty())
.sorted_by_key(|block| cfg.range(*block).start())
.peekable();

while let Some(block_range) = unreachable.next() {
let start = block_range.start();
let mut end = block_range.end();
while let Some(next_block) = unreachable.next_if(|nxt| nxt.start() <= end) {
end = next_block.end();
// Advance past leading reachable blocks
while blocks.next_if(|block| reachable.contains(block)).is_some() {}

while let Some(start_block) = blocks.next() {
// Advance to next reachable block
let mut end_block = start_block;
while let Some(next_block) = blocks.next_if(|block| !reachable.contains(block)) {
end_block = next_block;
}
let start = cfg.range(start_block).start();
let end = cfg.range(end_block).end();

checker.report_diagnostic(Diagnostic::new(
UnreachableCode {
name: name.to_string(),
Expand Down
Original file line number Diff line number Diff line change
@@ -1,4 +1,34 @@
---
source: crates/ruff_linter/src/rules/pylint/mod.rs
---
unreachable.py:18:5: PLW0101 Unreachable code in `after_return`
|
16 | def after_return():
17 | return 1
18 | / print("unreachable")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need multiline span diagnostics so that we can highlight the "why". (CC: @ntBre might be a good first rule to port)

With our current noqa system. Would a user have to put the noqa on the last line? Would that be confusing if they have

return 1

if a:
	pass
else:
	other # noqa: unreachable

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's the opposite: noqa comments go at the start of the range. So I think it would be

return 1

if a: # noqa: unreachable
	pass
else:
	other 

Playground example with existing rule

19 | | print("and this")
| |_____________________^ PLW0101
20 |
21 | def after_raise():
|

unreachable.py:23:5: PLW0101 Unreachable code in `after_raise`
|
21 | def after_raise():
22 | raise ValueError
23 | / print("unreachable")
24 | | print("and this")
| |_____________________^ PLW0101
25 |
26 | def multiple_returns():
|

unreachable.py:28:5: PLW0101 Unreachable code in `multiple_returns`
|
26 | def multiple_returns():
27 | return 1
28 | / print("unreachable")
29 | | return 2
30 | | print("unreachable range should include above return")
| |__________________________________________________________^ PLW0101
|
18 changes: 18 additions & 0 deletions crates/ruff_python_semantic/resources/test/fixtures/cfg/jumps.py
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
def only_return():
return

def after_return():
return 1
print("unreachable")
print("and this")

def after_raise():
raise ValueError
print("unreachable")
print("and this")

def multiple_returns():
return 1
print("unreachable")
return 2
print("and this")
37 changes: 33 additions & 4 deletions crates/ruff_python_semantic/src/cfg/graph.rs
Original file line number Diff line number Diff line change
Expand Up @@ -192,8 +192,12 @@ impl<'stmt> CFGBuilder<'stmt> {

/// Runs the core logic for the builder.
fn process_stmts(&mut self, stmts: &'stmt [Stmt]) {
let start = 0;
for stmt in stmts {
// SAFETY With notation as below, we always maintain the invariant
// `start <= end + 1`. Since `end <= stmts.len() -1` we conclude that
// `start <= stmts.len()`. It is therefore always safe to use `start` as
// the beginning of a range for the purposes of slicing into `stmts`.
let mut start = 0;
for (end, stmt) in stmts.iter().enumerate() {
let cache_exit = self.exit();
match stmt {
Stmt::FunctionDef(_)
Expand Down Expand Up @@ -223,10 +227,30 @@ impl<'stmt> CFGBuilder<'stmt> {
Stmt::With(_) => {}

// Jumps
Stmt::Return(_) => {}
Stmt::Return(_) => {
let edges = Edges::always(self.cfg.terminal());
self.set_current_block_stmts(&stmts[start..=end]);
self.set_current_block_edges(edges);
start = end + 1;

if stmts.get(start).is_some() {
let next_block = self.new_block();
self.move_to(next_block);
Comment on lines +234 to +238
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems a bit repetitive. We may want to abstract this somehow (e.g. store stmts in the current block and have a self.branch(offset) or similar). But I'm fine deferring this a little longer

}
}
Stmt::Break(_) => {}
Stmt::Continue(_) => {}
Stmt::Raise(_) => {}
Stmt::Raise(_) => {
let edges = Edges::always(self.cfg.terminal());
self.set_current_block_stmts(&stmts[start..=end]);
self.set_current_block_edges(edges);
start = end + 1;

if stmts.get(start).is_some() {
let next_block = self.new_block();
self.move_to(next_block);
}
}

// An `assert` is a mixture of a switch and a jump.
Stmt::Assert(_) => {}
Expand Down Expand Up @@ -269,6 +293,11 @@ impl<'stmt> CFGBuilder<'stmt> {
self.current = block;
}

/// Makes new block and returns index
fn new_block(&mut self) -> BlockId {
self.cfg.blocks.push(BlockData::default())
}

/// Populates the current basic block with the given set of statements.
///
/// This should only be called once on any given block.
Expand Down
1 change: 1 addition & 0 deletions crates/ruff_python_semantic/src/cfg/mod.rs
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,7 @@ mod tests {
use test_case::test_case;

#[test_case("no_flow.py")]
#[test_case("jumps.py")]
fn control_flow_graph(filename: &str) {
let path = PathBuf::from("resources/test/fixtures/cfg").join(filename);
let source = fs::read_to_string(path).expect("failed to read file");
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,81 @@
---
source: crates/ruff_python_semantic/src/cfg/mod.rs
description: "This is a Mermaid graph. You can use https://mermaid.live to visualize it as a diagram."
---
## Function 0
### Source
```python
def only_return():
return
```

### Control Flow Graph
```mermaid
flowchart TD
node0["return"]
node1((("EXIT")))
node0==>node1
```

## Function 1
### Source
```python
def after_return():
return 1
print("unreachable")
print("and this")
```

### Control Flow Graph
```mermaid
flowchart TD
node0["return 1"]
node1((("EXIT")))
node2["print(#quot;unreachable#quot;)
print(#quot;and this#quot;)"]
node0==>node1
node2==>node1
```

## Function 2
### Source
```python
def after_raise():
raise ValueError
print("unreachable")
print("and this")
```

### Control Flow Graph
```mermaid
flowchart TD
node0["raise ValueError"]
node1((("EXIT")))
node2["print(#quot;unreachable#quot;)
print(#quot;and this#quot;)"]
node0==>node1
node2==>node1
```

## Function 3
### Source
```python
def multiple_returns():
return 1
print("unreachable")
return 2
print("and this")
```

### Control Flow Graph
```mermaid
flowchart TD
node0["return 1"]
node1((("EXIT")))
node2["print(#quot;unreachable#quot;)
return 2"]
node3["print(#quot;and this#quot;)"]
node0==>node1
node2==>node1
node3==>node1
```
Loading