Isodus

I'm trying to make sure I understand load balancers and especially scaling them to large N:N values.

To keep things simple say I want a 9:9 load balancer. Can I arrange the belts in a 3x3 grid. Do one set of 3:3 load balancers for the columns, then do another set of 3:3 load balancers for the rows, and it all works out?

From my understanding, any one of the 9 belts after this should then equally drain all 9 upstream belts, correct?

For some reason RustRover is only recognizing numpad numbers as the macro keys they also represent.

In other words pressing `NumPad-1` will only register as `End` for keyboard shortcuts. Turning on numlock does not change this behavior.

Is there some setting that I need to change or is this a bug in the IDE?

Pose is position + orientation, but I've been trying to find if there is a standard term for pose + configuration of a robot.

ABB uses robtarget but I would be surprised if that's the standard term.

From looking into it I've found both "model" and "posture", but I have no idea if these are specific for a manufacturer or standards in robotics.

Is there a tracker for bugs/issues/suggestions? Nothing came up when I did a search.

I know there was an issue with elemental facets not showing up on hope shorn scythe, so I don't want to spend a ton of resources trying to get that if it's still bugged.

As far as I'm aware. there is no way to craft rings and their stats can vary.

For instance, I have a ring of agility but I'd like to reroll the stats to get better stats.

Lore wise, I think Cerim are the only ones who can use (and see?) the whispers.

However sacrificing random items (64 mushrooms or some other mass stackable item), doesn't really seem to make sense and just feels meh.

I would think something more like performing actions in the area of the whisper (killing mobs / gathering resources) would net some experience/knowledge/other-token-name towards evocation.

Or is there something else in the works?

I have an enum U that is commonly used wrapped in an option.

I will often use it converting from types I don't have defined in my crate(s), so I can't directly do the impl in the title.

As far as I have come up with I have three options:

1. Create a custom trait that is basically (try)from/into for my enum wrapped in an option.

2. Define impl From<T> for U and then also define `impl From<U> for Option<U>.

3. Make a wrapper struct that is N(Option<U>).

I'm curious what people recommend of those two options or some other method I've not been considering. Of the three, option 3 seems least elegant.

For example, I want to write a couple functions, they both would be doing the basically the same thing but one would be pulling from the "no_std" feature of a crate and the other would not.

If possible, does the feature flag need to be excluded/included at the file level? Or could this even be done within a given file?

I have a thread that has a few polling items on them where the poll function is not async.

I want to know when these polled items are ready as soon as possible, but if I don't put some sort of throttle (currently tokio interval), then cpu use spikes as the thread spins too fast.

However, by putting in the throttle, I'm introducing artificial lag to the system.

Ideally I'd like to put these items in some sort of return that is async so that I can just do a select on two futures (one mpsc to tell me to close the thread).

I've been wondering what the best practice is for defining a dependency in the workspace vs in local crates.

I've come up with a few different options, but I'm curious what others think is best.

1. Never use workspace dependency, every crate always defines their own uniquely. The benefit and detriment is that crates are then able to diverge in what versions they use. So if you want to update versions, you have to crawl through every crate, which is kind of a pain.

2. Only define dependencies in the workspace if they are used in multiple crates. The benefit is updating versions is centralized, but then you may break and have to fix multiple crates when you update. Minor downside is if

I've been trying out RustRover for a little bit and while I like it a lot, I'd like to be able to add icons to the gutter.

Clippy errors, warnings, and change suggestions. Also typos. Really any of the items in the inspect list.

They all already have icons too that show up elsewhere, but just not in the gutter.

Is this possible?

Currently I find it a little difficult to locate the any lines with errors, warnings, or typos.

Is it possible to highlight the text background (like how when you select text), or put an icon in the gutter to better indicate the line?

I know that there's an icon in the scroll bar, but that doesn't line up with the line so it's not that great of an indicator in my opinion.

My company is currently in the middle of converting our stack to rust and hopefully I can convince them to hire a few more software engineers in 2025.

This will be the first time I'm involved in the hiring process for any company and looking for advice to prepare.

I am making some side panels and I am wanting to achieve two things:

1. When middle clicking on the separator, I want the panel to rest to some default size.

I have been trying to see if there is a response I can hook into for the separator, but I don't see anywhere that gets spit out.

2. When the window resizes, the panel should maintain the same ratio (but within the width range) as it was before the resize.

Is there a window resize event I can hook into from the context for this? Or is there a configuration option I can do to the side panel that already does this?