Promoting good habits is good but this is health advice from an unlicensed commenter to say rice and beans is better than taking a statin. Consult your doctor if you’re curious what to do.
Every day I am shocked that books in the public domain on Kindle don't have X-Ray enabled. I am unable to find a copy of War and Peace for instance with X-Ray so I can keep track of all the characters and places. I'm not saying the world isn't going to shit but AI can help fill in feature gaps that the big-box developers have not bothered with.
I saw the ToC request as a demo of the capabilities, not a statement on the full value proposition. There are a LOT of valuable features in here that are not offered in Kindle or other ebook readers.
Selection of metal, lamination, presence of a ura (裏), handle material, the ability to make a new handle and attach it to the original metal. A metal chosen for an extreme sharpness may be terribly difficult to sharpen, a metal easy to sharpen may not hold an edge for long.
You are directionally correct but the top of the line chisels are in fact hand made in Japan and I suspect the same for knives. Lee Valley and some other higher end manufacturers make some damn fine chisels but chisels are hand tools and I would guess 9/10 woodworkers who use chisels will choose hand made Japanese chisels over any factory manufactured tools.
If you don't see the contradiction in JPL having an active research project to put a radio telescope on the moon and your original statement then I guess we'll have to agree to disagree.
You didn't read the article, it _specifically_ mentions JPL's proposal for the Lunar Crater Radio Telescope concept "nasa’s Jet Propulsion Laboratory (J.P.L.) is also exploring the idea of a radio-wave detector, the Lunar Crater Radio Telescope (L.C.R.T.), inside a 1.3-kilometre-wide moon crater."
Thank you again, I'm not able to determine if any of this is contrived but it's turned into a great teaching opportunity. I am highly impressed with Rust. The compile error looks extremely expressive of the core issue. I'm also new to zig if you can tell but this has helped me position the two languages and their goals better.
Thank you for that explanation. In the original blog post an example is shared of reusing a buffer, and I was curious how Rust would handle that scenario. Perplexity suggested the following:
// Use a mutable slice to represent the buffer:
let mut buffer = [0u8; 16];
// Read into the buffer:
let n = socket.read(&mut buffer)?;
// To move the partial second row to the beginning, you'd use
safe operations like:
let second_row_start = 7; // Index where second row starts
buffer.copy_within(second_row_start.., 0);
// Then read more data into the remaining space:
let remaining_space = &mut buffer[9..];
let additional_bytes = socket.read(remaining_space)?;
Is it possible for the rust compiler to statically determine if two memory regions will overlap at compile-time, especially with complex pointer arithmetic or when pointers are passed as function arguments? It would be super impressive if so.
I predict it will be difficult for people to reason about this without their biases around COVID, one way or another. Personally EEE sounds terrifying.
The author and the reviewer universally want "good code" but how often is that defined for any project? Clear definitions of what is important to your team and your code base would alleviate a lot of these antipatterns.