assets.get can take any kind of handle

[mockersf]

Objective

• assets.get can take an Handle<T> or an HandleId

Solution

• it's using the value as a HandleId anyway, so just expose it as needing the trait

[HoNile]

Good but if get change I think get_mut should do the same, and I guess contains too.

[tim-blackbird]

I'm not sure about this. This removes a type check that prevents Handle<Mesh> from being passed into Assets<Image>::get for example.

Then again, a lot of the other methods already take Into<HandleId> :(

[IceSentry]

Yeah, I'm with ira on that one, the typecheck seems valuable here.

[james7132]

Doesn't HandleId carry type/asset path information in it already? If we pass a Handle<Mesh> into a Assets<Image> it will always fail. Though, I guess that's a silent failure that should be caught at compile time, if possible.

[infmagic2047]

It was actually changed from Into<HandleId> to Handle<T> in #4794 for the typecheck 😄