Max Orok

What kind of error format would you like to see? `clang`, `rustc` and recent `gcc`s come to mind for good error messages, and there's some nice error formatting documents here:...

Yes, that makes sense :). From what I understand, we've got - an error span location of type `SrcLoc` with error start and stop file, line and column info -...

Hello @mehran1234, This sort of error can arise from either problems in the input file or bugs in the code. More information is likely required to resolve it. Does the...

This is ready for review and edits. There is a fairly convoluted commit history, and I would say squashing everything might be the easiest way to integrate it. I tried...

Hi @ftessier, everything looks great, thank you for that!

Hi guys, I encountered a similar issue trying to combine 1000 egsdat files where the combine routine stopped after processing the `w499` file. ``` ... 498 tmp_w498.egsdat ncase=10000000 cpu=129.97 499...

I took a look at skipping over bad data files but it was more complex than I expected. Skipping files with errors is straightforward, but making sure the application's state...

Hi @rtownson, sorry to barge in on this issue. Is this the case for all ausgab objects or just tracks? Maybe we could add a check in `EGS_Application::addAusgabObject` to catch...

Sure thing, thanks Reid! :)

I wanted to note that C++11 added RANLUX to the standard library: https://en.cppreference.com/w/cpp/header/random (`ranlux24`, `ranlux48`). It might be worth comparing the performance of both implementations, perhaps the standard has some...