What’s your goal with switching languages? You need to figure out what business requirements are fulfilled more effectively given that technical change before making that change. I mostly say this because I don’t hear a clear reason for the switch in your post.

For the rust ecosystem in general, reading through the cargo help output to see what tooling is there is a great start. You can see what functionality is already baked into the native language tooling, which should guide you on the right path. Off the top of my head, theres ways to test and lint your code already built in. Best practices are usually crate dependent, especially when working with something (I think) is macro heavy like dioxus(I don’t do a lot of UI in rust). Make sure to go through the provided dioxus code examples because those will probably cover most use cases you’ll be going for.

Yeah what I wrote was just something to get the idea out, about having a list of Allowables.

I just fully read your code, and I like how you changed the Allowable api to have a deny and allow function instead of it being at the AllowList level. Honestly, I did not know mem::take was a function. I like how you got around cloning too.

Also, just so you know, you come off pretty rude. Just want to make sure you know that if you’re not aware.

Also sorry, I realized I worded my response a little rude earlier. Didn’t mean it like that, I was just speaking matter of factly!

How is it a code smell? I’m pretty sure interior mutability is a well established design pattern. I’m not really familiar with the pattern you’re describing using Ref/RefMut wrapping, could you show me what you mean?

Yeah I didn’t want to pour a bunch of time into wrangling borrow checker stuff for a small code snippet.

Finally got around to writing the code, here’s the link to the Rust playground with it. I was too lazy to do the unsafe stuff, but where I call clone in the deny and accept functions are where you’d rewrite and do unsafe magic to swap out elements without the clone overhead.

I also tried to implement a take function (like in Option) for the Allowable enum. Transferring ownership like with take would keep you in safe land and get what you want done.

Keep in mind I am not a game dev. I don’t do cache optimizations. I have no idea how this code would function in a game context, but this is just my first idea for implementation of what you asked.

I don’t think you need a mutex for this situation.

What are the conditions for T to be accessed? You could potentially wrap each instance of T in an enum that has two states, Allow and Deny, where if you encounter a Deny you just don’t access that one. If you have a slice of this enum where each enum owns T, you can always just swap out a Deny for an Allow or vice versa depending on how you want to do it. If you go this route, you might want to make a struct that owns the vector mutably, can return an immutable borrow to the slice, and change permissions on the slice. Now that I’m thinking about it, you can also implement a gets function on the struct that would return a Result<T> depending on whether it was an allow or a deny. I don’t think you’d need unsafe with this.

The solution mostly depends on the context surrounding how you’re managing what can access T and at what time. I can see the solution I proposed not working if you need more specific permissions than allow or deny, or if the permissions are based on the caller.

Edit: I’m going to come back in a few hours and write code about what I mean in the first paragraph.