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
TWIR CFP - Difficulty: medium. Requires knowledge of Windows APIs and unsafe FFI handling.
The winapi crate, while not deprecated, hasn't received an update since 2020. This is because the windows and windows-sys crates have completely supplanted it.
Clearscreen has a bit of winapi code to write terminal escapes and configure the console:
While this code is stable, it would be a nice, self-contained refactor to move it to the windows-sys crate.
As part of this refactor, assess the unsafe usage in the new code, adding appropriate // SAFETY: comments. There is no need to audit the existing unsafe code as part of this task.
The text was updated successfully, but these errors were encountered:
Hi, I am very interested in contributing to this issue. Although I am new to Rust and this would be my first time contributing to open-source, I am eager to learn and would greatly appreciate any guidance to help me address this task. While I will do my best to make progress promptly, I may require additional time and support to ensure the solution meets the project’s standards. Thanks
Note
TWIR CFP - Difficulty: medium. Requires knowledge of Windows APIs and unsafe FFI handling.
The winapi crate, while not deprecated, hasn't received an update since 2020. This is because the
windows
andwindows-sys
crates have completely supplanted it.Clearscreen has a bit of winapi code to write terminal escapes and configure the console:
https://github.com/watchexec/clearscreen/blob/main/src/lib.rs#L791-L821
While this code is stable, it would be a nice, self-contained refactor to move it to the windows-sys crate.
As part of this refactor, assess the unsafe usage in the new code, adding appropriate
// SAFETY:
comments. There is no need to audit the existingunsafe
code as part of this task.The text was updated successfully, but these errors were encountered: