Félix Fischer

Two things make me love teaching.

The first one is to empower others. Fuck yeah fam, you'll conquer that cliff, and entirely with your own might.

The second one is to kindle their curiosity. There is nothing quite like seeing the eyes of someone who just got to love the world a little bit more.

For what it's worth, if you survive long enough to taste a soluble lithium salt, know that it will probably be very citrusy. Like zesty even :3

Python Software Foundation Sponsors The official home of the Python Programming Language

Forget about supporting the PSF, too abstract.

Pip installs from PyPI. It would be bad if `pip install` stopped working. Support the org that runs PyPI.

Surprise, it's the PSF! Your company depends on #Python. You want it to keep working and keep being good.

python.org/psf/sponsors/

semantically breaking change.

One can find similar examples of semantically minor changes as well.

So anyway. The type systems we use are incomplete. And we must keep that in mind when thinking about them, in relation to how we might be breaking things downstream.

it describes a Total Ordering (a relation over a set that is Reflective, Antisymmetric, Transitive and Total). However, this contract is not expressible in the signature of the trait. One could change an Ord impl to not be a Total Ordering anymore. This doesn't change the signature, but is a

All of them. Since the signature cannot express all of its behavior (at least not in... regular type systems), some of the behavior of a function might be part of its "contract" even though it is not expressed in its signature.
Take an implementation of Ord, for example. Part of its contract is that

Hell yeah Morre Morri Arrt!

Being normal be damned. Be weird instead ❤️

Also, :'c 🫂

Fwiw I always read your blog posts :3 they be very good.

The rest are fasteners and stuff, which are most likely not nutritious, yet probably made out of steel and thus survivable

The engine, oil and gas I'm guessing we'll treat like the excretory system: to be discarded during meal prep

If you're planning on eating an airplane, definitely get an oldie!

May I recommend a very old one? Nowadays they're made of aluminium, which would definitely be toxic in those amounts.

Very old models used mostly wood and fabric for their bulk. I bet that with good cooking, one could strip away the varnish and such things, and get something that's survivable.

Our society's moral failing isn't lack of "civility" or "respect for different viewpoints". It's that so many views are lacking in empathy/compassion that they support a government spending billons in weapons while scoffing at the idea of spending fractions of that to feed, clothe, and house people.

This has nothing to do with anything.

It's finally warm enough to swim. So, I swam today for a handful of minutes.

I love water so much 💖

The official home of the Python Programming Language

TLDR; The PSF has made the decision to put our community and our shared diversity, equity, and inclusion values ahead of seeking $1.5M in new revenue. Please read and share. pyfound.blogspot.com/2025/10/NSF-...
🧵

Help me, what did they do? I'm out of that loop owo.

Hmm. 65:35 split

2F03
(Looks small but weird. Turns out it's the year 12035 in a society that changed year representation to hexa)

If I get lucky again, I will go to Rustweek next year. Will you be there? I would love to go chill with you and talk about whatever :D

But then someone asks them in just the right way, and a small spark starts a chain of events that end up in a roaring fire of curiosity in their mind. Like "WAIT so how tf do they do it in A, or in B?!?!", and "how did anyone manage to estimate this decently for generic hardware???"
(2/2)

I wonder if they were underestimating how hard the problem is? Because... perhaps it's the kind of thing they take for granted, or believe is solved trivially in a couple lines of code or a lookup table of some kind.
(1)

🤣

It's a good interview question! I think.

I mean... at the very least the estimating technique would be very interesting to discuss.

That, plus also what to do depending on what information is available (eg disk fragmentation, bus availability, the specific filesystem's special properties...)

Estimation

Maybe they hired the same guy?

Relevant xkcd: xkcd.com/612/

Your voice acting is gooooood, dude! For reals! :>

If there is a choice between being earnest with how you feel and not doing so, picking earnestness is always best 💖

(To be clear: it's still impossible to reason about divergence (not returning-ness) in general, because of the halting problem. But an approximation is better than giving up the goal!)

It's very good documentation that's also expressible in the type system. And that also enables tooling to reason about it.

Like e.g. in safety critical you may want to be very strict about calling things that don't return. And with !, approximating such a thing becomes more tenable :)

Oh wow, the threads below have shared a lot of what I knew.

Before I forget to mention it, there's another thing in ! that's helpful, and that is: to be more explicit in intent.

Being able to say that a fn will never return is super nice: "this is an infinite loop; assume I don't return".

yet no ! that implements both at the same time can exist. Does that make sense? I hope that makes sense.

Another way to put it would be that there is an entire lattice of types above !, there's a set of nodes in there that implement Drop and another that implement !Drop, but those sets are disjoint

Awww! Dang it.

vvv Re: ambiguity error vvv

I actually don't know how it works internally.

But if I understand the structure of the type lattice underlying it, ! can be coerced into anything, as long as it (the thing) exists. So one ! could implement Drop, and another ! could implement !Drop,

....

Picric versioning, which is when as soon as the code dries, it becomes an explosion hazard.