[compute] Apply fold expressions

[ragmani]

This commit applies fold expressions.

ONE-DCO-1.0-Signed-off-by: ragmani [email protected]

[ragmani]

With Fold Expressions

Pros:

Conciseness: Eliminates boilerplate code such as explicit loops or temporary arrays, resulting in more succinct code.

Declarative Style: Clearly expresses that a condition must hold for all elements, improving readability for those familiar with the construct.

Compile-Time Evaluation: When applicable, the fold expression is evaluated at compile time, potentially reducing runtime overhead.

Cons:

Steep Learning Curve: Developers unfamiliar with C++17 fold expressions may find the syntax confusing or non-intuitive.

Debugging Challenges: Errors or unexpected behavior within fold expressions can be harder to trace compared to traditional loops.

Limited Flexibility: For complex operations that require different handling for each element, a fold expression may be less adaptable than an explicit loop.

---

Without Fold Expressions (Traditional Loop)

Pros:

Familiarity: More developers are accustomed to traditional loops, which can lead to easier understanding and maintenance.

Easier Debugging: Iterative code is often simpler to step through and debug, as each iteration is explicit.

Flexibility: Allows for more complex logic per iteration, offering greater control when different processing is needed for each element.

Cons:

Verbosity: Requires more boilerplate code, such as loop constructs and possibly temporary containers, which can clutter the code.

Imperative Style: The intent of "all elements must satisfy a condition" is less declaratively expressed compared to a fold expression.

Potential for Errors: More explicit code may lead to mistakes (e.g., off-by-one errors) that are less likely in a concise fold expression.

[ragmani]

The structure UNUSED_ALL can be replaced with (void(check_shapes), ...);. But There are no overhead difference, readability, and conciseness.

[seanshpark]

LGTM