oxcrow

Thanks for implementing this feature! 🚀

Thank you for your feedback and suggestions. I really like the examples you have made, since they can be used with any number of ranks. I think experts can easily...

Most likely the code hangs during an error on one rank, because of : - blocking `recv` on other ranks - `barrier` on other ranks In case of other errors,...

Here's a proof of concept. Barrier seems to be partially responsible. As, if we remove the barrier, the app crashes on *all* ranks. ```rust fn crash() { use mpi::traits::*; let...

Could something else be done to handle such errors? If the ranks keeps running indefinitely then it would be a problem. I was thinking what if we could detect if...

I did, ```rust /// Parse the source cdode and create an AST pub fn parse_string(source: &str) -> Result { pest::set_error_detail(true); let parse_tree = IxParser::parse(Rule::file, source)?; Ok(()) } ``` We get...

I support this enhancement request. Even within the same git repo it is beneficial to use the `fast forward` and `no fast forward` methods of merging to ensure we retain...

@stefanhaller thank you for providing an alternative solution. Regarding if "only few people need such an option" I would say that is correct. However that is because most people use...

**Potential Solution?** Surprisingly, - Using `ok` works. - Using `ok()` causes the bug. I have no idea why this happens. ```fortran ! Surprisingly this works! #define ok if(ie/=0) then; return;...

**Why do I need such macros?** It would be nice if we could use the `ok` macro to handle errors easily. I just use it to return from a subroutine...