# Please, No More Loops (Than Necessary): New Patterns in Fortran 2023

**URL:** <https://fortran-lang.discourse.group/t/please-no-more-loops-than-necessary-new-patterns-in-fortran-2023/10605>\
**Category:** Uncategorized\
**Created:** [January 7, 2026, 8:08pm UTC](https://fortran-lang.discourse.group/t/please-no-more-loops-than-necessary-new-patterns-in-fortran-2023/10605 "2026-01-07T20:08:38Z")\
**Posts on this page:** 1\
**Showing post:** 82

<div class="post-metadata">

**Author:** ![hkvzjal](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/hkvzjal/32/3055_2.png) [@hkvzjal](https://fortran-lang.discourse.group/u/hkvzjal)\
**Post date:** [January 30, 2026, 9:51am UTC](https://fortran-lang.discourse.group/t/please-no-more-loops-than-necessary-new-patterns-in-fortran-2023/10605/82 "2026-01-30T09:51:46Z")

</div>

> [@CRquantum](#):
>
> if printing can cause crashes or segfaults

Sorry, maybe I wasn’t clear. I didn’t mean the print causing the crash. What I meant is: your application might crash or segfault for which ever reason, then you want to know why, so you switch the debug mode, but now everything works… so you might need to go back to release mode but putting prints to find where the problems is by dichotomy. This is what I meant by “debug by printing as your last resort”. The reasons for a crash or segfault in release not happening in debug mode are multiple and I prefer not to bloat this thread with that topic.

---

_[View the full topic](https://fortran-lang.discourse.group/t/please-no-more-loops-than-necessary-new-patterns-in-fortran-2023/10605)._