Even if you were using the builder pattern, this maintains the immutable variable in the parent scope while you use the mutable variable’s builder pattern methods (basically exactly as my example demonstrates) in the inner scope.

edit: Oh, I think you mean you would chain the builder pattern calls and assign it to an immutable variable. Sure, that makes sense if you own the struct.

I prefer to encapsulate a mutable reference to the instance in a scope.

let post_form = {
    let mut post_form = PostInsertForm::new(
        // your constructor arguments
    );
    post_form.some_mutating_method(
        // mutation arguments
    );
    post_form
};

This way you’re left with an immutable instance and you encapsulate all of the logic needed to setup the instance in one place.

What did he whisper in her ear?

The runoff voting downside is incorrect, the “drag the voters up to yellow and watch how it makes red win” example. This is not “see how making yellow more popular makes yellow lose”. It’s actually “see how making red more popular than yellow makes red win”. The movement of the voters is not for yellow, but for red and yellow in a way that gives more voters to red.

There is no way for yellow to be the only candidate to get a boost of voters in the demo. If there were, it would only demonstrate further that yellow would still continue to win.

Runoff voting is the way.

There are some people who both start and end every gun debate with the “good guy with a gun” argument. Nothing gets through the impenetrable logic of “it makes sense to me”.

If she says “You didn’t ‘lock her up’ like you promised” he’ll just turn it around on her and claim that she should be locked up. Chats of “lock her up!” will begin as they completely ignore anything negative said about him.

I don’t know how to get everyone I know to really understand this. Every time I bring it up in conversation, the other person just puts their hands up and explains that they’re powerless to address it, so it’s not even worth talking about. I don’t know how to respond to the apathy.

Yeah, if it’s purely a Sqlite implementation detail to create temp files, that’s on them to own and fix. I thoroughly dislike that the files are obscured from users.

Oh, I thought that the temp files were named by the user. If that’s not the case, that these are not databases created specifically by McAfee in the temp directory, then I’m not sure what the appropriate solution should be. Obscuring the file type and how the file is used from users is still a bad practice.

I love how the solution didn’t involve changing the prefix to “mcaffee_”. Now users don’t know who to blame. Great. That’s so nice of them.

Your team needs to have a coding standards meeting where you can describe the pros and cons of each approach. You guys shouldn’t be wasting time during PR reviews on the same argument. When that happens to me, it just feels like such a waste of time.

I’d love to include my wave function collapse library, but examples of its usage in games is lacking atm. I’ve thought of a couple games that could be made that utilize the concept, but I haven’t prioritized them.

For those that are interested: https://github.com/AustinHellerRepo/WaveFunctionCollapse

hook to Insomnia plays

“Normal transaction” after a fundamental change in how all games that use your product are financially responsible by novel, unmeasurable, and unrealistic metrics. No transaction prior to this kind of announcement is “normal” imo.