@Bert-Proesmans Thank you for the Answer, it really helped me to develop my idea of the project.
I have currently two approaches where I cannot decide which one is the better idea or has the better use case.
The first one: catching runtime errors in rust is kind of boring because rust hasn’t that much runtime errors, much more while compile time. Furthermore, there are not many (i didn’t even found once) example of a runtime error in StackOverflow. Runtime errors in rust are basically self-made by panic!() and are often found in extern dependent crates. But I couldn’t test it appropriately because StackOverflow hasn’t issued about runtime errors from extern crates (as I researched).
The second one: It would be nice to refer compile-time errors to StackOverflow. The docs aren’t always understandable and it would be good if you have some other helping resources from SO. So then I would need to wrap a broken program to analyze the compile errors and give an adequate output with links referring to possible solutions. But the most Editors have already builtin cargo servers which check compile errors in real-time.
In the one hand, I need to catch runtime errors which basically not issued on Stackoverflow or in the other hand refer compile-time errors to better-explained solutions, although there are good builtin cargo servers which do the same but with Rust docs.
What do you think would be the better use case? Or maybe you have another suggestion?