@ekuber@hachyderm.io
@ekuber@hachyderm.io avatar

ekuber

@ekuber@hachyderm.io

"We spent decades trying to invent a sufficiently smart compiler when we should have been inventing a sufficiently empathetic one."

Rust Compiler team member. If you have to search for answers when the compiler is talking to you, that's a bug.

There are no bad programmers, only insufficiently advanced compilers.

Cache-locality awareness evangelist.

๐Ÿ’ผ@aws, opinions my own

he/him

Trans rights are human rights

This profile is from a federated server and may be incomplete. Browse more on the original instance.

ekuber, to rust
@ekuber@hachyderm.io avatar

Sometimes I wish that rustc had a database of small breaking changes that affect only a handful of crates, so that we could on the fly patch them going forward. Things like "we now correctly check for lifetimes in assoc types" can technically be a breaking change that affects a handful of crates, but I want to ensure that building a project from today in 15 years doesn't require a compiler tool chain from today.

I guess this is the windows backwards compatibility approach.
#rust #rustlang

ekuber,
@ekuber@hachyderm.io avatar

It could even be for providing specific errors instead of "just make it work", telling people what magic changes might be needed to patch the outdated library.

ekuber,
@ekuber@hachyderm.io avatar

@matthiaskrgr we could be able to. We could downgrade the error to a warning then ๐Ÿค”

ekuber,
@ekuber@hachyderm.io avatar

@chrisg we already do for a handful of things. Macro handling comes to mind. The principled answer is "editions", of course.

ekuber,
@ekuber@hachyderm.io avatar

@chrisg I guess so. The problem is the maintenance burden of alternative behavior for fundamental checks, but that's kind of what we signed up for with editions.

ekuber,
@ekuber@hachyderm.io avatar

@kornel you would want to make patch releases for pretty much every affected dot release, but that would likely be the best option.

trkohler, to random

@ekuber hello! Any chance you may want to present on Rust Ukraine 2024 conference?

ekuber,
@ekuber@hachyderm.io avatar

@trkohler when is it happening? It would depend on the timing.

ekuber, to rust
@ekuber@hachyderm.io avatar

" development is going too fast (because they are stabilizing features I don't care about) and going too slow (because they are not stabilizing features I care about!"

There are only so many contributors, hours in a day, days in a year to get to everything now, and some features are reliant on other, less flashy work that needs to happen before they can be even attempted.

But people are putting in a lot of work, the codebase changes so quickly that it is hard to keep up.

ekuber,
@ekuber@hachyderm.io avatar

If you think we're too fast, look at the release notes and tell us what we shouldn't be landing.

If you think we're too slow, look at the release notes and tell us nothing is happening.

ekuber,
@ekuber@hachyderm.io avatar

@ironchamber it is very common in open source. I just saw someone complaining that there won't be a Rust 2.0 and using that as proof that the project had ground to a halt ๐Ÿคท๐Ÿปโ€โ™‚๏ธ

Everyone has an opinion, which I've learned to pick apart for actual useful feedback, but every now and then I see something soon off the mark that it is not even wrong.

ekuber,
@ekuber@hachyderm.io avatar

@manpacket has there been any feedback on the fcp yet? Wrangling checkbox ticking can be difficult (particularly from users with lots of notifications). Do not forget that the backcompat requirements of the project are so high that it's hard to gain confidence or agreement on any user visible change. It's not ideal.

ekuber,
@ekuber@hachyderm.io avatar

@manpacket by the way, thank you for rolling up your sleeves and working on it.

My rant was directed at people who don't, yet volley critiques that are not borne from reality. Your concerns are very real.

ekuber,
@ekuber@hachyderm.io avatar

@manpacket yes.

Feel free to send me the link to the RFC and I'll take a look at it.

jhpratt, to rust
@jhpratt@mastodon.social avatar

Hit an edge case in the compiler that appears to be quadratic at best and potentially exponential. Trivial to make happen with real-world code. Investigating...

ekuber,
@ekuber@hachyderm.io avatar

@jhpratt looking forward to the repro and either finding out that it is a 2 line fix or requires a complete reimplementation of 2 stages of the compiler.

ekuber,
@ekuber@hachyderm.io avatar

@jhpratt @predrag replacing bodies with loop {} is the first step I do, I'm guessing this is on some where bound or impl Trait return?

ekuber,
@ekuber@hachyderm.io avatar

@jhpratt @predrag I'm sure @errs will be looking forward to the report ๐Ÿ˜€

hds, to random
@hds@hachyderm.io avatar

@ekuber I just missed the fn keyword and found that the error message in that case wasn't so helpful.

error: expected one of ! or ::, found (

I couldn't find a issue for this, but I thought I'd check with you before creating one.

ekuber,
@ekuber@hachyderm.io avatar

@hds go ahead and create one. I know there's a generic one about parsing things that don't belong in trait and impl blocks, but this is more targeted.

foone, to random
@foone@digipres.club avatar

Properly photographing a 3.5" floppy disk for archival is annoyingly complicated. The label has THREE sides!

I've already built an automated system to take a picture of the front of a disk, but really I need to take THREE photos if I want to get the whole thing.

That means either three cameras or I need to rotate the disk 90ยฐ and then 180ยฐ, which is going to really stress the limits of my mechanical engineering skills.

ekuber, (edited )
@ekuber@hachyderm.io avatar

@foone wouldn't focus and vibration be mitigated by fast shutter speed and high f stop? Then what you need is either high ISO or a lot of light. Alternatively you could see if you can automate your set up to use focus stacking for the different planes.

ekuber,
@ekuber@hachyderm.io avatar

@foone there are some cheap used DSLRs with autofocus that might be easy to drive for this purpose, cheaper than a new cheap camera.

GrapheneOS, to random
@GrapheneOS@grapheneos.social avatar

An experimental prerelease of GrapheneOS for the Pixel 8a is now available via https://staging.grapheneos.org/ including web installer support. It will be made available via https://grapheneos.org/ after we've done basic testing including testing the upgrade path to a future release.

ekuber,
@ekuber@hachyderm.io avatar

@GrapheneOS is this in the new Rust Bluetooth stack or the previous system?

ekuber, (edited ) to photography
@ekuber@hachyderm.io avatar

ekuber, (edited )
@ekuber@hachyderm.io avatar

@onelson Nikon 80-200 f2.8 ED @ 200mm f5.6

ekuber,
@ekuber@hachyderm.io avatar

@onelson about 6 meters. Didn't seem to have a self preservation instinct. There were two and both came closer than that.

noth, to rust
@noth@ilyamikcoder.com avatar


ah yes

ekuber,
@ekuber@hachyderm.io avatar

@noth you might not like it, but this is what peak performance looks like :o)

ekuber,
@ekuber@hachyderm.io avatar

@luis @noth https://knowyourmeme.com/memes/this-is-the-ideal-male-body

ekuber,
@ekuber@hachyderm.io avatar

@luis @noth don't sweat it, there's no obligation to be up to date with obscure Twitter memes from 8 years ago

  • All
  • Subscribed
  • Moderated
  • Favorites
  • โ€ข
  • provamag3
  • rosin
  • InstantRegret
  • ethstaker
  • DreamBathrooms
  • mdbf
  • magazineikmin
  • thenastyranch
  • Youngstown
  • GTA5RPClips
  • slotface
  • Durango
  • khanakhh
  • kavyap
  • megavids
  • everett
  • vwfavf
  • tacticalgear
  • osvaldo12
  • cisconetworking
  • cubers
  • modclub
  • ngwrru68w68
  • Leos
  • anitta
  • normalnudes
  • tester
  • JUstTest
  • All magazines
    •