# Copy pwd into clipboard using pbcopy
alias cpwd="pwd | tr -d '\n' | pbcopy && echo 'pwd copied into clipboard'"

.# grep search the current directory function lg() ls -alt grep $1

The main one that jumped out to me was a scroll issue on iOS when using multiple fingers. I just looked it up to share a link and it may be fixed? It’s the mentality of “Eh, we might fix it one day” that is the bulk of why I didn’t stick with Flutter. A bug this annoying lingering for as long as it did said volumes to me.

Possibly fixed: https://9to5google.com/2023/12/28/google-fixes-flutter-infamous-scrolling-bug/

I wanted to get into Flutter but it seems like there are some bugs that are either unfixable or that they have actively decided not to fix. I didn’t want to end up wasting my time building on such a foundation, but it’s definitely nice for certain projects that fit within the supported functionality.

Can anyone explain what this means to me like I’m 5?

This was a great blog post. I love Rust and Bevy, but I can definitely see why you made the switch.

The primary issue with your decision to use Rust/Bevy, for me, was that you were taking on the task of getting others to work in a difficult language for novice developers. I would never suggest Rust as someone’s first language, coupling that with a regularly-changing library like Bevy.

I would love to know what the pros and cons were between Unity and Godot. If you were going to switch to C# anyway, Godot seems like the next logic choice to me, so I’m curious about what your team’s evaluation was for that engine.

Exactly. The functions of the super trait are also required when implementing the child trait’s functions, as you would expect from inheritance.

Basically, you can generalize your trait types into their parent (super) traits for situations when functionality is specific to those supertrait objects.

As an example, if you have a trait CanBark and it is a super trait for the trait IsDog, you can coerce your references of &dyn IsDog into a &dyn CanBark. You can then work with other trait types that share a super trait.

trait CanBark {
    fn bark(&self);
}
trait IsSeal: CanBark { }
trait IsDog: CanBark { }

fn bark_as_group(barkers: &Vec<&dyn CanBark>) {
    for barker in barkers {
        barker.bark();
    }
}

let spot: &dyn IsDog = get_spot();
let seal: &dyn IsSeal = get_seal();
let barkers: Vec<&dyn CanBark> = Vec::new();
barkers.push(spot);  // coerced
barkers.push(seal);  // coerced
bark_as_group(&barkers);

At least, I hope this is possible now. If it’s purely “you can return a coerced type from a function”, that is less useful.

Wow, that trait feature is great. I’ve been eagerly waiting for that one for a long time. Thank you to everyone who made that possible.

When I learned Python I thought that not having a statically typed language was the way to go, but then it just became an issue when I was trying to ensure that everything was at least something like what I was expecting. Going back to statically typed languages even harder with Rust has been a dream. I love it.

I’ve found that one of the best things to do when making a library for something that is going to have a web interface is to first have it work in the terminal. You can much more quickly play around with the design and fix issues there instead of having to work with a more complex web interface.

You just create a simple menu system, like input("1: Feature A\n2: Feature B\n>") and just start trying out all of the different scenarios and workflows.

Sounds good. Please share what you find and what you end up going with.

There are a few different ways to solve this problem without using unsafe and I’m not sure what would be considered idiomatic. Another option is to ultimately encapsulate all of the nodes in a reference-counted box like Rc or Arc and specify the type of your parent/child/sibling references to the same reference-counted box type. With that, you just share cloned instances around as needed.

The primary drawback here is that for mutable access you end up having to perform a lock every time on an underlying Mutex (or something similar). You also no longer have direct access to the singular instance of the node.

There are pros and cons to every approach.

One way of solving this is to structure all of your nodes into a HashMap with the node ID as the key and the node type as the value. The underlying node type could have node IDs for referencing purposes. You lose the ability to reference the parent/child/sibling directly, but you avoid direct circular dependencies. That said, now you need to manage dangling references for when the node is removed from the main HashMap collection.

deleted by creator

“Maintainable code and common patterns? But I prefer code-golfing my if-statements into one, long sequence of characters.” -coworker standing atop the Dunning-Kruger peak

I hate that it came to this, after so many Rust devs left, but all I can say is “Good.”

It was over a matter of honor, of course.

The README helped a lot, thanks. Just wanted to point out a minor typo, I think the second word under the “Client” section is meant to be the word “client”.

deleted by creator