Bevy’s great! If you already know Rust or want to learn Rust, it’s a really fun code-first framework to use

Remember kids: document your code changes!

Alright, that was pretty straightforward. This is the reason I try to write detailed PR descriptions. I know my memory would not have served me well had I not left good notes for myself 😅

github.com/bevyengine/b...

I still think it's pretty cool I managed to get this working at all

```rust
// Allows adding two `i32`, `u32`, or `f32` numbers
let reflect_add = add::<i32>
.into_function()
.with_overload(add::<u32>)
.with_overload(add::<f32>);
```

This was merged towards the beginning of the 0.16 cycle back in December so I actually forgot about it up until now lol

Actually, we can do `clone_value` -> `to_dynamic` and `clone_dynamic` -> `to_dynamic_***`.

This should allow us to properly deprecate all the replaced methods rather than just removing them outright!

So I think I can try renaming the conflicting methods on the reflection subtraits to things like `to_dynamic_struct`.

That's a little unfortunate because I wanted to make this a non-breaking change.

Alternatively, I could try to find a better name for `clone_value`.

I think the next thing I'd like to work on is some more minor type data and/or macro improvements since it would at least be nice if those coincided with the `reflect_clone` PR landing in 0.16 as well

github.com/bevyengine/b...

Okay hopefully that does it (accidentally imported `bevy_reflect` instead of `bevy::reflect` in an example).

Normally, I'd wait for all of CI to pass but my son has an early appointment tomorrow. I enjoyed finally having an hour to work on some #bevy code though 😭

Actually, CI is failing. Hold please!

Aaaand we're done! Just goes to show that sometimes a PR looks scarier to rebase than it actually is 😄

Final commits were super easy: first was just adding a compile fail test (only had conflicts due to a change I made in the first commit) and the second was just a tiny bug fix.

First commit down! Mostly just renames that git couldn't handle. But seems there have been quite a few new `FromType` usages added to the repo since almost a year ago, including a dedicated type data example!

My usual checks are passing, so moving on!

I try not to squash as I like to break my commits into manageable parts with a (somewhat) clear timeline. For large PRs this preference can really be a pain.

Thankfully, this PR only has 3 commits :)

This PR should also fix a mild annoyance of mine that `FromType` should really be given a name more apparently related to "type data"