Skip to content

Commit 25d18a0

Browse files
authored
Apply suggestions from code review
1 parent 688c804 commit 25d18a0

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

src/2026/tail-call-loop-match.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,7 @@
77
| Tracking issue | |
88
| Other tracking issues | https://github.com/rust-lang/rust/issues/112788, https://github.com/rust-lang/rust/issues/132306 |
99
| Zulip channel | |
10+
| [lang] champion | @scottmcm |
1011

1112
## Summary
1213

@@ -40,7 +41,7 @@ In light of these design issues, we'd also like to continue development of `loop
4041
| Team | Support level | Notes |
4142
| ---------- | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
4243
| [compiler] | small | We expect to only need normal reviews. |
43-
| [lang] | ? | Some architectures cannot support guaranteed tail calls. Our current list of limitations is:<br><br>- `wasm32`/`wasm64` need the `tail-call` target feature to be enabled<br>- `powerpc` (when `elf1` is used) cannot tail call functions in other objects<br><br>Hence, rust code using guaranteed tail calls is not as portable as standard rust code. We need T-lang feedback on how to resolve this.<br><br>The all-hands is well-timed to figure out a solution. |
44+
| [lang] | Medium | Some architectures cannot support guaranteed tail calls. Our current list of limitations is:<br><br>- `wasm32`/`wasm64` need the `tail-call` target feature to be enabled<br>- `powerpc` (when `elf1` is used) cannot tail call functions in other objects<br><br>Hence, rust code using guaranteed tail calls is not as portable as standard rust code. We need T-lang feedback on how to resolve this.<br><br>The all-hands is well-timed to figure out a solution. |
4445

4546
## Frequently asked questions
4647

0 commit comments

Comments
 (0)