ekuber

ekuber, 8 months ago to rust

If there were an opt-in lint you could run on #Rust code to assert a function you've written will never panic, how would you want (the default) to be when handling method calls on trait objects where some impls might panic? Error given that it could panic or downgrade to warning given that we don't know for sure?

ekuber, 8 months ago to rust

#RustConf 2023
@nellshamrell's "Rustacean Community Interfaces" talk in full swing, talking about the many hats rustaceans wear.
#rust #rustlang

image/jpeg
image/jpeg
image/jpeg

ekuber, 18 days ago to rust

Request for feedback: how would you change this #Rust compiler error? Can you tell what's going on? What the problem is? Do you get a sense of how you might be able to solve it?

#RustLang

ekuber, 8 months ago (edited 8 months ago) to rust

Meet Red Pen, a rudimentary #Rust linter: https://github.com/estebank/redpen
I cleaned things up to the point where you can actually use this, but it is v0.1 and I mean it. It most likely won't work when you first try it (linux only for now), but I'm really happy with the first useful lint it has: assert that a function cannot call panic.

PRs very welcome.

ekuber, 3 months ago to rust

What would you take out of this #Rust diagnostic? Is this too much information? Would you prefer to have a shorter message at the cost of needing multiple cycles of the compiler telling you you're missing a change?

ekuber, 1 month ago to random

Every time there's a CVE affecting some fundamental part of modern computing that Rust provides a dot-release for, it seems multiple publications find out first from the Rust blog and publish titles implying that Rust is the only affected thing. It's not only mildly annoying hearing the echos of "har, har, I thought it was 'safe'", it does a complete disservice to anyone that doesn't use Rust because they won't find out they have to update or mitigate the issue too!

ekuber, 9 months ago to rust

I have some thoughts on the subject of Telemetry and Metrics in the context of the #Rust tooling. I want to hear your feedback on the matter.

"No telemetry in the Rust compiler: metrics without betraying user privacy":
https://estebank.github.io/rustc-metrics.html

ekuber, 7 months ago to rust

Hot take: #Rust is not the end-all be-all of languages. Other languages will come forth with improvements in multiple axes. I also think that it has made a lot of good choices on trade offs, but some of those make it harder than it could be. I think there's space for an EasyRust, that could be developed independently, but it could be part of the same existing codebase and leverage it as a testing ground for changes to Rust itself. You could even say that nightly is that language already.

ekuber, 4 months ago to random

I finally started reading Dune. A quarter of the way in and can see why it is such a beloved classic.

ekuber, 8 months ago to random

I said "I want fn foo() -> impl enum Display { if rand_bool() { 42 } else { "hi!" } that creates an anonymous enum that impls the trait" over a few beers after RustConf, and the range of expressions from 😨 to 😈 of the people there was hilarious 😅

ekuber, 10 months ago to rust

I'm super proud whenever a #Rust newcomer asks a question in a forum, and the response is "if we run the code you want, the compiler tells you this, which explains why it can't doesn't work", and then goes on to expand. I'm terribly against RTFM attitudes, but Read The Friendly Compiler Output should be a valid learning strategy.

ekuber, 10 months ago to rust

Has anyone tried to do a pure-#Rust protocol buffers serialisation/deserialization implementation? As much as being able to wrap over libraries with a C ABI easily is a great Rust feature, dealing with non-Rust dependencies can sometimes be annoying.

ekuber, 3 months ago to random

Perhaps unsurprising observation that caught me by surprise at first: people don't read error messages.
It might read "say 'friend' to enter" and users will stand around in a circle next to a monster infested pond as if you had given them a riddle.

ekuber, 6 months ago to rust

Dashboard with #Rust versions as seen by crates.io with the information provided by cargo:
https://p.datadoghq.com/sb/3a172e20-e9e1-11ed-80e3-da7ad0900002-973f4c1011257befa8598303217bfe3a?refresh_mode=sliding&from_ts=1699226397081&to_ts=1699831197081&live=true
Thanks to @tb for this!
#RustLang

ekuber, 8 months ago to Albuquerque

Last week there was a "pro second amendment" protest in #Albuquerque in front of the town hall.

Three people half hearing the stump speech, one all in dark clothing holding an American flag, one in -tacticool clothing, and one with cowboy hat, red plaid shirt and jeans with a long rifle on his back.
A handful of people hearing the speaker, with a bunch of right wing flags hanging in the background.
A handful of people hearing the speaker, one person holding an American flag in the middle.

ekuber, 8 months ago to random

"You can say 'all are welcome,' but if wolves and sheep are both welcome then you're only going to get wolves. The the smart sheep will go somewhere else and the naive sheep will be eaten and processed. [...] Refusing to choose is a choice. It's a choice in favor of the people who prey on others and who refuse to acknowledge the humanity of those they hate."

ekuber, 7 months ago to rust

The #Rust project on Mastodon: https://social.rust-lang.org/@rust

ekuber, 11 days ago to rust

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, 4 months ago to random

I am now a citizen of the United States of America.

ekuber, 3 months ago to rust

Regular reminder that if a #rust compiler error isn't clear, we consider that a bug. File a ticket! Worst case scenario it gets closed as a duplicate. Second worst it takes us a long time to get to them. But I assure you I've read every single open A-diagnostics ticket at least twice.

ekuber, 1 month ago to rust

Somewhat cursed #RustLang idea: "attributes at a distance"

#![attr(target = crate::foo::Bar)]

mod foo {  
 struct Bar;  
}  

What would you use this for?

ekuber, 11 days ago to rust

"#Rust 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 #RustLang 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, 9 months ago to random

"When people tell you what doesn't work, they're usually right. When they tell you how to fix it, they're usually wrong."
– Bill Hader

I couldn't have come up with such a succinct way to frame it. You need to listen to people complaining about problems, but don't over index on the solutions they propose.

ekuber, 3 months ago to rust

impl dyn Foo + 'static where Self: 'static {
fn hello(&'static self) where Self: 'static {}
}

For when you want to really be sure that your #Rust trait object method is invoked on an owned type.

ekuber, 1 month ago to rust

Rust's unexpected super-power is just how flexible it is. It allows you to write very high level looking code on a low level language. That caused people to use it beyond its intended niche. But it is fundamentally a low level programming language. It will continue becoming easier to use (that's my personal goal!) but there are "obvious" changes that would make things easier at the cost of speed or correctness that #Rust cannot take.
#RustLang