You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error handling is a significant part of any project, historically we picked error-chain as an option for dealing with this, at the time it was the defacto standard in rust. This has changed by now and the project has grown to the point where error-chain can become cumbersome and maintain as an error handling framework. This project aims to solve this problem by taking the time to investigate alternatives and reset error handling to a fresh start.
This comes with a few requirements:
Errors need to be helpful for users, this is the main priority.
Errors should be easy to add - in the past string errors have quickly crept in since adding new error cases was complicated and effort-intensive - simplifying this will lead to better maintainability
Support for hygienic errors especially for script failures (pointing to the location in the code) and hints
Support for structured logging
Accessibility - we should present errors in a way that is accessible to all users
Good cross crate support - the codebase includes a number of crates and we will need to be able to handle errors sensibly over crate boundaries
Performance is quite relevant, the error framework can not slow down execution on the hot path
A library or framework should be well maintained in the hope that it is long-lasting
Async support, while error handling is likely not affected by this it is worth keeping in mind since a lot of our code is async based
Ideally, error propagation and attribution to call paths would be helpful in many situations
Very optional, an ‘issue’ database, to link issues id’s to
Hi @Licenser , I am Rishabh,Final year computer engineering student at Delhi Technological University.I wanted to say that I am interested in this project. I am intermediate c++ Developer and have good knowledge of Data Structures and Algorithms and also I know basics of rust language.Can you please tell me about the prerequisites for this project in LFX Mentoship program except than Rust programming language.
Error handling is a significant part of any project, historically we picked error-chain as an option for dealing with this, at the time it was the defacto standard in rust. This has changed by now and the project has grown to the point where error-chain can become cumbersome and maintain as an error handling framework. This project aims to solve this problem by taking the time to investigate alternatives and reset error handling to a fresh start.
This comes with a few requirements:
A few related issues are:
report.json
gets generated even when the-o
flag isn't specified #1072Possible frameworks that have come to mind are (this is a non-exhaustive list):
The text was updated successfully, but these errors were encountered: