LLMs don't usually make trivial language mistakes like supposively.
I think this is just a really inexperienced or unskilled developer. Or possibly a very dedicated troll.
FizzyOrange
joined 1 year ago
It actually works. I tried poetry once and it failed to resolve some simple dependency specification.
Ok you can say it was a fluke bug but it didn't inspire confidence.
uv is also freakishly fast. My venv setup times went from 57 seconds to 7 seconds. I seriously doubt Poetry can do that because it's written in Python.
Right... I mean the idea is obvious so why even bother with any of it? The only interesting reason is to demo that it actually works in reality which clearly they didn't.
Ah I see, though they don't seem to be for sale so I don't think this guy actually has access to them.
Yeah it's definitely a vast improvement on previous attempts (Poetry et al).
I dunno if it can be called solved until it's officially sanctioned and installed by default though, and I don't see that happening for a very long time.
Kind of worthless video. Just speculates about how it works. They don't ever even show the app working!
These glasses aren't even AR so the idea that they can overlay details as shown in the mockups is impossible.
It was clearly a joke.
My advice is that you debug via tests. If you install Rust-analyzer (you probably already have) then any tests you add have a little "Run test" and "Debug test" button next to them that you can just click. It magically works without having to faff around with JSON files.
As for your current setup, as other said you have an issue in Cargo.toml which is unrelated to debugging, and the target binary is in target/debug, not in the workspace root.
One of the things I hate about merge-based Git workflows is git makes a default Merge 123234234 from user/dave/fsdf message which:
a) Is shit - it contains zero useful information (what's in the change??) and contains information you explicitly don't care about (the temporary branch name the author happened to use). a) Makes people think they are supposed to use that message.
It would probably be better if the default message was blank. But also squash & rebase is generally better anyway and it avoids this problem entirely.
Wow, they (apparently) finally made the REPL not suck! I always thought it was weird how shit it was given that it's one of the big reasons Python has become as popular as it is.
Maybe in another 20 years they can make the package tooling not suck too.
I dunno it looks well designed but I dunno why I would use it instead of Rust.
On Arduino it's 16 bits. (At least the original ATMEL ones; I dunno if they've finally moved to ARM yet.)
This lost me quite a lot of time when I tried to use their SD card library on a 32-bit Arduino and it hung due to some code assuming
intwas 16 bits.