← Feed

Posts

• View post

  calling everything in the python ecosystem 0ver if it hasn’t bothered to go to epoch 1 1!0.0.1 is a much more legit stable release than 1.0.0 (aka 0!1.0.0)

• View post

  important update: 💹 is now the pleading emoji for pegging 💹😳💦 my currency is so unstable it needs to be pegged 👉👈

• View post

  the ^default place in carbon’s proposed ownership model, defined as “the set containing all places that aren’t named”, really has me hoping they add ^russell, “the set of all place sets that don’t contain themselves” (^places are similar to rust’s 'lifetimes, so the analogous concept in rust of 'default in a function signature would be a lifetime that contains all elided lifetimes... so like you could do fn<'a>(&'a u32, &u32, &...

• View post

  tbh very enamoured with this terrible plumbing job a contractor did while openly admitting he super fucked up because he was sleep deprived

• View post

  anyway just learned python typing invented a new kind of voldemort type -- one which when named doesn't actually name it `float` and `int` are two distinct types in the type system but if you write `x: float` that actually means `x: float | int`. but if you write `x: float | int` that means `x: float | int | int`. anyway that's why `ty` has a `JustFloat` extension that is an actual alias for actual `float` that doesn't expand to `float | int`, so you can actual refer t...

• View post

  periodic reminder that "but we have so much old code, surely adding more analyzers to catch bugs in all the old code is much higher impact than piecemeal writing new code in a memory-safe language" has been repeatedly demonstrated to be a falsehood by the android team https://security.googleblog.com/2024/09/eliminating-memory-safety-vulnerabilities-Android.html

• View post

  function subtyping is easy, just remember you use **contra**ceptives when putting it inside and a **co**pay when taking it out