@RL_Dane Hell, my personal opposition to Rust only exists because of the cult.
I, for one, have no real basis to have a strong opinion on Rust. It seems like it might have good ideas, but it uses LLVM so it's not worth looking into. The centralized package management is a mistake, IMO; Go got the package management model pretty much right.
Saying "I prefer C" has attracted negative attention (and moral judgements!).
My opposition to Rust is entirely a result of the insane undeserved hype.
@RL_Dane@jbowen
If you make 145 line additions and 129 line removals in one of your core algorithms of 313 lines and all your ~50 tests pass on the first try you just fall in #love with #Rust. It's inevitable at that point. ¯_(ツ)_/¯
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?
Currently in the process of rewriting my #transpiler from #nom v4.2 to #chumsky v1.0.0-alpha.6 🤓
It is a lot of fun so far, but I have to say these type signatures are wild!😄
I'm still struggling with it far more than I'd like, but I guess it is just a matter of time until intuition kicks in and it will become more and more natural.
Exciting project ahead!🙂
I'm even able to parse string literals with escape sequences - something I haven't even achieved with nom!
Also, the examples in the docs are quite numerous and should be fairly helpful. The crate examples show you how to grow everything into a more non-trivial design.
@josiah I mean, we had @jnolis writing about using R in prod at T-mobile 5 (!) years ago! And the context there implies that it's getting hit a bunch, if it's being used to classify customer responses.
@Stark9837@diazona@d_k_bo ?: Is best girl for sure. Lots of languages use it that way since C/algol/smalltalk set the stage for it. Kind of hate any alternative tbh. Lua even has an unused ? Token and they still opted out. Rust at least does this amazing thing with it for error bubbling so I'll forgive it.
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?
@ekuber I'm not saying it should be disallowed. I'm saying it has bad UI. People get into such situation by accident, are unaware when it happens, and a simple cargo update can add dupes to a no-dupes project without informing the user, and without straightforward ability to undo that.
@ekuber yeah, that's the "it's possible" case that bothers me, because two different versions of one dependency at the same time shouldn't be possible in the first place.
Disallow this, and the entire ecosystem has to adapt, and will adapt.
Allow it, and every project will be susceptible to having that, and endure the side effects...
@markuswerle@laund Well, it's nice that you get to work on your own code that has no bugs.
When you have some practical advice on how to reduce the number of bugs in a codebase that is 30+ years old, billions of LOC and worked on by 10,000+ engineers let me know.
Honest question for the #rust developers out there. I've observed several pretty high profile OSS projects recently, which are written in rust but are not cross platform. Well at least as far as Unix is concerned, it's Linux or nothing.
This is super unfortunate, not only as a #BSD user it locks me out from using these tools...but it also introduces a pretty big blind spot in terms of development which can lead to fragile and/or insecure systems. The whole "monoculture is bad" thing.
So folks hacking on #rust - what do you feel is lacking that makes it easier to write portable code?
Hey @xmpp folks, if I was to encourage the devs of a messaging server/client written in Rust to implement XMPP, with MUC and OMEMO, what would be the best links to send them for guidance?
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?
Here is the last version of the diagnostic. First is the case people are realistically going to encounter, second is the "worst" possible case. Last one is what it looks like now. Feel free to give feedback!
The code that produces it is at https://github.com/rust-lang/rust/pull/121274 #Rust#RustLang
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.
@janriemer Currently, TS is the best available option. WASM is the future, but it is not there yet. I mean, you get problems if you try to launch a thread…
This video is about #Rust, but it's comments about error handling are valid for anyone in any language. PHP friends especially, this is the kind of stuff I've been ranting about for a while now. :-)
Be me: waiting for a bus at a bus stop next to a greek diner. A homeless guy steals a beer from the diner. The owner chases him and demands his money. A brawl starts. Me calls the police. The operator: "Did some of the participants said they want the police. Could you ask? That is nothing for the police until someone is seriously injured"
I experienced a segfault in my brain whilst invoking $police->call($violentSituation);
Usually it's for the police when someone calls the police.
But it's also the reason why I took the firebrigade as example. 'Cause WHEN they are called, there is no holding back. They don't ask whether someone actually wants them. They will be there!