I’m a Christian and software engineer; I create random graphics projects and websites. Feel free to ask me for help with programming, or about my faith!
I believe you are correct; if the unsafe code can cause undefined behavior if input data is not following a specific contract, then the entire function should be labeled unsafe so the caller knows that.
The other option is to check to make sure the contract is valid, and return an error or panic if it is not. That function would be sound, as no inputs cause undefined behavior.
Check out Ollama and its extensions for VSCode; might save you some money paying for other services if your computer can run models locally.
The link they use is working for me; what is the code you are using to fetch the data?
Also, dbg!() is a very useful macro for inspecting state. Might help see what is going on.
That link seems broken (the date is wrong). This worked for me:
https://this-week-in-rust.org/blog/2023/11/08/this-week-in-rust-520/
I haven’t taken it myself, but “The Last Algorithms Course You’ll Need” is free and is written by The Primeagen. He works at Netflix and runs a programming-focused YouTube channel, and as far as I can tell is very knowledgeable and level-headed.
Learn Rust With Entirely Too Many Linked Lists is a great example of how references work (or don’t work) in more complex situations. Might seem like a lot at first, but working through writing the code yourself and seeing the compiler’s responses is a great help when learning Rust. It also doesn’t hurt to read it once and then come back and read it again later, after you try writing some more programs.
For anyone who is confused: This is exploiting an old soundness bug in the Rust compiler that is still present. The GitHub issue page has this comment from maintainers: