If you consider that these suggestions would be helpful for the community, feel free to add them to the
so people can vote and they might be taken into account for future releases.
Regarding your second suggestion, the reason that some interfaces and implementations remain in the same assembly is to keep a simpler usage and avoid you having to add more
references to your projects, or if you prefer to consume the library as source code, avoid having several projects in your solution. Having separate assemblies for interface would trigger an assembly explosion that goes against the
simple first principle.
Keep in mind:
This is not necessarily the final design of the assemblies. The drops will most likely undergo modifications until the official release.
Please let me know if this helps.