bevyengine / bevyengine/bevy

Add non-short-circuiting run conditions and re-rename short-circuiting run conditions to be explicit

Open
#13,793 10 comments 0 reactions 0 assignees View on GitHub
A-ECS C-Docs C-Usability X-Contentious
Dominant language
Rust
Stars
48.2k
Forks
4.8k
Avg merge
3d 22h
Merged PRs (30d)
161

Description

While that's an important fact about how these work, I don't think this naming convention was doing a good job conveying this information to users. As evidenced by the fact that users regularly asked "why is it called `and_then`", and answerers didn't point to "oh that's because it's short-circuiting".

IMO we should use clear, simple names, and explain this behavior better in documentation and other learning material.

_Originally posted by @alice-i-cecile in https://github.com/bevyengine/bevy/issues/13784#issuecomment-2158904149_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.