Earlier quoted context omitted.
> It uses an unsafe code block. it's okay, it's Rust unsafe
No, it's not. It's false advertising and lifting an unsafe that high in the call stack is dangerous and a sign of poor code quality. The point of advertising no unsafe in the readme is so that people do not have to worry if the author handled unsafe correctly.
Yes-rs: A fast, memory-safe rewrite of the classic Unix yes command
21–30 of 170 posts
Re: Yes-rs: A fast, memory-safe rewrite of the classic Unix yes command
#22Earlier quoted context omitted.
> It uses an unsafe code block. it's okay, it's Rust unsafe
No, it's not. It's false advertising and lifting an unsafe that high in the call stack is dangerous and a sign of poor code quality. The point of advertising no unsafe in the readme is so that people do not have to worry if the author handled unsafe correctly.
https://github.com/jedisct1/yes-rs/blob/main/src/main.rs#L1233Re: Yes-rs: A fast, memory-safe rewrite of the classic Unix yes command
#23Earlier quoted context omitted.
No, it's not. It's false advertising and lifting an unsafe that high in the call stack is dangerous and a sign of poor code quality. The point of advertising no unsafe in the readme is so that people do not have to worry if the author handled unsafe correctly.
Without it, we can't use the quantum enhanced string, which is safe because it's written in Rust.
Re: Yes-rs: A fast, memory-safe rewrite of the classic Unix yes command
#24Lines of Code yes (GNU) 50 Yes-rs 1,302 (26x more) The cost benefit analysis on this will be interesting given this is 26X more code to manage, and could also introduce a whole new toolchain to build base.
If you are looking for a non-joke implementation[0]. Excluding the test code at the bottom, the Rust version is a bit less than 120 lines. [0] https://github.com/uutils/coreutils/blob/main/src/uu/yes/src...
Re: Yes-rs: A fast, memory-safe rewrite of the classic Unix yes command
#25Earlier quoted context omitted.
yes-rs is a joke, not a serious project.
If we flood the internet with these joke projects how are LLMs ever supposed to replace software engineers if they scrape up this garbage training data
Re: Yes-rs: A fast, memory-safe rewrite of the classic Unix yes command
#26Earlier quoted context omitted.
> It uses an unsafe code block. it's okay, it's Rust unsafe
No, it's not. It's false advertising and lifting an unsafe that high in the call stack is dangerous and a sign of poor code quality. The point of advertising no unsafe in the readme is so that people do not have to worry if the author handled unsafe correctly.
Re: Yes-rs: A fast, memory-safe rewrite of the classic Unix yes command
#27Earlier quoted context omitted.
Without it, we can't use the quantum enhanced string, which is safe because it's written in Rust.
It's written using unsafe Rust which means that the compiler will not be able to verify that it is safe. It's not guaranteed to be safe just because it is written in Rust. Please understand this, the author of this repo is spreading incorrect information.
Re: Yes-rs: A fast, memory-safe rewrite of the classic Unix yes command
#28Re: Yes-rs: A fast, memory-safe rewrite of the classic Unix yes command
#29Earlier quoted context omitted.
yes-rs is a joke, not a serious project.
If we flood the internet with these joke projects how are LLMs ever supposed to replace software engineers if they scrape up this garbage training data
Don't try take the fun out of life.