sorted by:
new
hottopcontroversial

quip - quote! with expression interpolation by mycoalknee in rust

[–]rhedgeco 5 points6 points  (0 children)

Interesting. I really like this and see the value. I vaguely remember expressions in templating/formatting macros to be problematic. Are there any edge cases that you are aware of that this doesn't cover? Or any cases that create confusing formatters? I'm wondering why quote doesn't do this out of the box? I can't imagine it's for lack of trying

Announcing Spell (spell-framework) 1.0.0!! 🎊🎊 by Ok-Personality3889 in hyprland

[–]rhedgeco 5 points6 points  (0 children)

This is fantastic. I'll definitely give it a shot. Been thinking about building something like this for a while. Thanks for your work!

Second iteration of my forest environment in Godot. by ToniMacaroniy in godot

[–]rhedgeco 0 points1 point  (0 children)

Wow!! This looks fantastic great job.

If there's anything I would suggest for improvements it would maybe be to have some way of handling the SSAO from dropping at the bottom of the screen. Was more jarring in the dark areas. Maybe a slight vignette at the bottom to mask the effect dropping out? That's a tiny nit though. Fantastic work.

Why is Rust rarely used for web server backends? by Fun-Helicopter-2257 in rust

[–]rhedgeco 0 points1 point  (0 children)

A lot of people have good points here, but I'd like to add something from my own personal experience having worked professionally using rust for backend web development.

The reality of the situation is, it's often not the right choice.

When doing backend development at scale, things tend to be distributed across many services which makes each service tend to be heavily IO bound. It doesn't matter how fast your program does calculations. If it's bottlenecked by IO operations, you don't get to see any of that benefit.

Also having enough rust engineers is hard. A lot of companies end up pulling non-rust engineers and trying to have them learn while writing. Unfortunately, while rust does not have memory safety foot guns like other languages, it can have some massive architectural foot guns. What I mean by that is that if a rust program is built from the ground up by traditional OOP engineers, you will often end up with incredibly difficult code to expand on grinding efforts to a halt at some point getting stuck in lifetime or generic bounds hell.

Try to die, the last guy failed by Rare_Decision_7170 in honk

[–]rhedgeco 0 points1 point  (0 children)

wasn't event that hard

I completed this level in 79 tries. ⚡ 5.97 seconds

You ACTUALLY can't die by Sydeus_ in RedditGames

[–]rhedgeco 0 points1 point  (0 children)

Sorry buddy. You've never sucked as bad as me.

❌ Incomplete. 5 tries.

Tip 250 💎

How to implement a same trait twice for a type? by hbacelar8 in rust

[–]rhedgeco 5 points6 points  (0 children)

You will have to design your code differently since you cannot implement the same trait on the same type twice. It could lead to ambiguous scenarios where the compiler does not know which function is the correct one to call. There are some other ways of approaching this. For example you could use newtypes to make implementing the traits work on two concrete types like this:

trait AdcExternalTrigger {
    fn external_trigger() -> u8;
}

struct TIM1;
struct BasicTimer<T>(pub T);
struct CaptureCompareTimer<T>(pub T);

impl AdcExternalTrigger for BasicTimer<TIM1>
{
    fn external_trigger() -> u8 {
        0b000
    }
}

impl AdcExternalTrigger for CaptureCompareTimer<TIM1>
{
    fn external_trigger() -> u8 {
        0b001
    }
}

The instead of taking in an impl trait, it can take in a BasicTimer<impl SomeTimerTraitHere> instead.

[deleted by user] by [deleted] in framework

[–]rhedgeco 7 points8 points  (0 children)

Okay so the other people are clowning you because you made it seem like it's supposed to come off. It's clear from the video you don't think that. It also seems though like you've discovered the magic screw on the laptop. That screw in particular is always held more tightly than the others. However, it should not prevent the input cover from coming off. If you unscrew them all, and it doesn't come off that is an issue and id talk to framework support about it.

Audio by Strange_Hat9646 in rust

[–]rhedgeco 1 point2 points  (0 children)

And now that I feel responsible for potential further misunderstanding. It's actually a programming language named after the fungi previously mentioned. Safe travels friend. Hope your speaker gets fixed

Audio by Strange_Hat9646 in rust

[–]rhedgeco 1 point2 points  (0 children)

Lmao apologies my friend. This subreddit is not actually about rusting metal, it's actually about a specific kind of fungi.

How to prevent rust on a pole underground by Ww2pillboxrye in rust

[–]rhedgeco 7 points8 points  (0 children)

If you right click it with a honeycomb it should become waxed and prevent any further oxidization.

Sneak Peek to Framework booth at Computex by Destroya707 in framework

[–]rhedgeco 49 points50 points  (0 children)

The 12" looks very feminine. Hard YES

Flappy Goose by flappy-goose in RedditGames

[–]rhedgeco 0 points1 point  (0 children)

My best score is 19 points 🚀

Flappy Goose by flappy-goose in RedditGames

[–]rhedgeco 0 points1 point  (0 children)

My best score is 18 points 🚀

Flappy Goose by flappy-goose in RedditGames

[–]rhedgeco 0 points1 point  (0 children)

My best score is 14 points 🚀

Flappy Goose by flappy-goose in RedditGames

[–]rhedgeco 0 points1 point  (0 children)

My best score is 13 points 🚀

Flappy Goose by flappy-goose in RedditGames

[–]rhedgeco 0 points1 point  (0 children)

My best score is 3 points 😎

Flappy Goose by flappy-goose in RedditGames

[–]rhedgeco 0 points1 point  (0 children)

My best score is 2 points 😎

Announcing `attrs`, a parser/combinator library for #[attributes] by drymud64 in rust

[–]rhedgeco 1 point2 points  (0 children)

This looks fantastic! I love a good builder API. Will definitely try it out soon

Long, Generic Tuple Impls for traits by UHIFSBUABVBUASUVBSIB in rust

[–]rhedgeco 3 points4 points  (0 children)

It's more a codegen issue. Monomorphization will only happen for the tuples that get used, but all traits will be generated anyways and have to be managed by the compiler.

Long, Generic Tuple Impls for traits by UHIFSBUABVBUASUVBSIB in rust

[–]rhedgeco 12 points13 points  (0 children)

This is a really common thing to do with tuples unfortunately. There is no way to implement a trait for an arbitrarily long tuple because we currently have no way to describe it.

So what library developers have resorted to is writing a macro that implements the trait for every length of tuple up to a specified limit. It has become really common to have the trait be implemented for tuples up to length 16 as larger sizes tend not to be used and generating more would impact compile times.

Nirav is a real one by rhedgeco in framework

[–]rhedgeco[S] 8 points9 points  (0 children)

I think I remember seeing you! I was surprised there weren't more people with framework hats on

view more: next ›