Next article =) How the borrow checker handles ifs and loops is a pretty fun topic. If-statements work like you'd expect (invalidations from both branches are merged). Loops is where it gets weird: we have to scout all the invalidations that happen inside the loop and then "replay" them _before_ the body of the loop. I can explain it more if you'd like.
I was wondering about the case where a reference points to a different path depending on control flow. I guess you can just design your language to make this impossible but this is still possible to do with pointers in C/C++.
Theoretically, we can have a reference that points to two paths, a "path union" so to speak. If the user explicitly typed out the path union, it would be something like:
let my_ref &Entity in (live_list[], dead_list[]) = if ...
though it would be nicer in practice, because the compiler could infer that.
Haven't implemented it yet of course, but the data structures in the borrow checker are designed with this in mind.
Yep, that comes for free from the model. Though, if you're asking if we can have two unique references (like `&mut`) to two different entries, not yet. Nick's original proposal had some thoughts on how we can do that, and Zeta (another language implementing group borrowing) has some neat dependent-type-ish mechanisms for that. I'm still considering what Valen will want to do there.
Tests can only prove the presence of bugs, but not their absence. If the AI can access the tests, it can easily make them pass by just adding additional if statements. It doesn't mean the code is actually correct.
Hover is done by the client telling the compositor it would like the cursor to change its shape if it is over a certain area the client is drawing. But the client does not know where the cursor is or where on the screen the client is (or even if the client is visible at all).
Oh, it was! But the guy that generated it insisted that he triple-checked the prose after, and it should be treated as typed by hand
I'm pretty sure it would be okay to stop at 5-10 questions, because it was clear he couldn't answer any. But my friend is from a hateful branch, and so she went for humiliation angle of asking for as much clarification as the ticket itself allowed
I have a very similar situation. Except it isn't even a ticket, just an export of a very long "conversation" with ChatGPT with a vague indication that this is what needs to be implemented. When questioned about it, the person insists they completely understood it before but just forgot after a few days. Sometimes the prompts are removed. Lots of contradictory material in it, some doesn't make sense even in context. Very difficult to figure out what is wanted.
> person insists they completely understood it before but just forgot after a few days.
I don't doubt this, to be honest.
I have the feeling of learning a lot when coding with agents. New features, patterns, entire languages... It's very satisfactory asking questions and getting answers in as much detail as you want, with examples, etc.
Except I forget it all soon after. Because I didn't put the effort. Easy come easy goes .
I'm continually flabbergasted that this is accepted and not immediate grounds for punitive action- plopping slop into a ticket (or having it generated directly) is straight-up disrespectful to the person on the other end. I'd rather have someone slap me in the face directly than get one of these tickets.
Stablecoins are just tokenized versions of exisiting currencies. Instead of settling through the current financial system which takes days for a global transaction you settle on a blockchain within seconds or minutes. These stablecoins will probably be issued on existing global blockchains like Ethereum so they might all be interoperable within a single system just like SWIFT currently supports multiple currencies.