Is there a reason that Forge's item handler doesn't merge incoming stacks with existing stacks first, but inserts into empty slot first instead? Is it performance?

where ??

27 minutes ago, diesieben07 said:

IItemHandler's insert method is slot based, you explicitly specify the slot you want to insert into. If you want this behavior, you have to implement it externally.

...and much of the container code that exists (e.g. the vanilla wrapper, many mod container's Transfer Stack methods) blindly goes "does this go in slot 0? Slot 1? Slot 2?" until it runs out of things to insert or places TO insert them. Why does it do this blindly? Because programming a blind insertion is easier: you don't have to look at any slot twice in order to guarantee that the insert succeeds.

14 hours ago, diesieben07 said:

IItemHandler's insert method is slot based, you explicitly specify the slot you want to insert into. If you want this behavior, you have to implement it externally.

Well, I implemented that in my custom handler. But I suppose it wouldn't be accepted in a pull request to Forge? I don't like that when, say, there is a stack in slot 12 with size 24, and a hopper inserts a stack with same item into empty slot 3 just because this slot happened to be found first.