Eager Eagle

if your tractor can’t run farming simulator, is it even a tractor?

Doing that with GNU or WINE will use your entire memory

of course nods along

I would. It’ll rule out if you need to do anything or just wait for your account to be a bit older.

A while ago I created an account with a Simple Login email and had a similar problem. In my case I just wanted to check an authentication via GitHub I had set up was working properly and couldn’t do it because they weren’t accepting the aliased email address. I reached out to support, but they basically told me to use a regular email address.

my favorite JS framework is HTMX for making me write less JS or even none at all.

I don’t think so. A half-measure using docstrings would likely take more processing power and require an ad-hoc implementation because comments are not broken down into ast components afaik. It would also be more costly in the long run if they decide to convert it into a proper syntax, as a result of docstrings not having a single standard way of being written.

Python has introduced several syntactic changes for type annotations, this is not unreasonable.

So you have to do dumb workarounds like declaring every bool values as bool | np.bool_ or casting bool_ down to bool.

these dumb workarounds prevent you from shooting yourself on the foot and not allowing JS-level shit like "1" + 2 === "12"

deleted by creator

I’ve been using copilot for a while to know it’ll be something like timeBottom and timeTop.

But if anyone’s getting this recommendation there’s probably not much code in that file or the code is trash. Garbage in, garbage out.

some heroes don’t wear caypes

that’s still a docstring, idk of linters that take docstrings into account at all. We need a semantic approach for this kind of annotation.

nothing wrong with that - it is an exception, as in, the customer is likely lost after that anyway.

Any validation you can write with a few early returns you can write with an equivalent conditional/s followed by a single nested block under it, followed by a single return. The reader is free to leave the validation behind just the same.

And that conditional indents your entire function one level - if you have more validation checks, that’s one level of indentation per check (or a complicated condition, depends whether you can validate it all in one place). It’s pretty much the case the other user illustrated above.

Returns inside business logic past validation is where the problematic bugs of this class show up

That much we agree. But again, this is not an early return issue, putting too much logic in a function is the issue. Rewriting it without early returns won’t make it much clearer. Creating other functions to handle different scenarios will.

You can say any execution flow controls are like gotos - continue, break, exceptions, switch, even ifs are not much more than special cases of gotos.

This is true regardless of the size of the function which shows that the size of the function isn’t the determinant

Logical clarity does tend to worsen as the function grows. In general, it is easier to make sense of a shorter function than a longer one. I don’t know how you could even say otherwise.

Early returns are still great for argument validation. The alternative means letting the function execute to the end when it shouldn’t, just guarded by if conditions - and these conditions any reader would have to keep in mind.

When a reader comes across an early return, that’s a state they can free from their reader memory, as any code below that would be unreachable if that condition was met.

I hate it when some blame early returns for the lack of maintainability.

Early returns are a great practice when doing argument validation and some precondition checks. They also avoid nested blocks that worsen readability.

What’s being described there is a function that tries to do too much and should be broken down. That’s the problem, not early returns.

I thought it was just incrementing the address and dereferencing it, but I don’t write C or C++. What is being overloaded there?

yeah, I just tried copying ~/.thunderbird, renamed the profile directory with the name betterbird created on startup and it worked.

They implement “minimize to tray”, but with the add-on “Minimize on close” I now have a “close to tray” behavior.

good point, I was going to months ago, but I was too lazy to migrate the accounts and forgot it existed until now

I just want a ‘minimize to tray’ ‘close to tray’ option on desktop, especially with the kdocker workaround not working on wayland.

I can’t believe thunderbird still doesn’t have this feature natively.