LINK : fatal error LNK1189: library limit of 65535 objects exceeded

**Bevy version**

0.4.0 (3b2c6ce49b3b9ea8bc5cb68f8d350a80ff928af6)

**Operating system & version**

Windows 10 64-bit (version 1709)

**What you did**

I was just following the setup instructions [here](https://bevyengine.org/learn/book/getting-started/setup/). When I tried to follow the `cargo run --features bevy/dynamic` step things seem to have gone awry though.

**What actually happened**

Got a linker error from bevy_dylib with this error code:

> LINK : fatal error LNK1189: library limit of 65535 objects exceeded
>
>
> error: aborting due to previous error
>
> error: could not compile \`bevy_dylib\`

**Additional information**

This is my first time messing with Rust and I'm not at all familiar with this kind of toolchain so there could very easily be something I'm doing wrong but I was just following the directions on the getting started/setup page so I'm not sure what I would have done wrong here. Looking around I've found old issues saying to try `rustflags = ["-Zshare-generics=y"]` but I have absolutely no idea where to put this and searching around is frustratingly unhelpful since every mention I can find of it it just someone telling someone to try it. Putting it in my project's cargo.toml seems to do nothing. I seem to have been able to accomplish the other steps on that page that come after without issue though. I did the LLD linker bit as well as the nightly Rust compiler bit and adding bevy in my cargo.toml dependencies. I also seem to have accomplished the copy+paste of code on the getting-started/apps and up to "Your First System" bit on getting-started/ecs so I'm not sure if this issue is something I have to worry about or not before continuing.

Start by reproducing the setup instructions and the `cargo run --features bevy/dynamic` command on Windows 10 with Bevy 0.4.0, including the reported LNK1189 error. Check the referenced LLD and nightly Rust setup steps and the attempted `rustflags` configuration. Done means determining whether the documented setup is incorrect or the command completes without the linker failure.

Written by the indexing model from the issue text.