Xeonitte: Refactor panic through code #1

New issue

Open

opened 2026-05-21 11:02:43 +00:00 by let_rec · 0 comments

let_rec commented

2026-05-21 11:02:43 +00:00

Owner

All `unwrap()`, `expect()`, and other panic-causing methods must be modified. As you can see, there are many similar codes.

Instead of using such methods, use anyhow for error handling and other methods, ways instead of unwrap().

### All `unwrap()`, `expect()`, and other panic-causing methods must be modified. As you can see, there are many similar codes. - Instead of using such methods, use `anyhow` for error handling and other methods, ways instead of `unwrap()`.

Screenshot From 2026-05-21 15-36-20.png

7.7 KiB

Screenshot From 2026-05-21 15-35-47.png

167 KiB

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

let_rec/Contributions#1

No description provided.

Rows
Columns

Xeonitte: Refactor panic through code #1

All unwrap(), expect(), and other panic-causing methods must be modified. As you can see, there are many similar codes.

All `unwrap()`, `expect()`, and other panic-causing methods must be modified. As you can see, there are many similar codes.