(Based on: #140, #139)

Hey, since you mentioned that you've enabled discussions and I would have a few more things to discuss I'll just take the freedom and make a new discussion.

Just Features

A bit of background, I'm manually loading and initializing all DLL relationships in my project. That means, that the "Logger" is using a default implementation before a C function is loaded and called from the application.

• Currently when using RCC++ I run into an issue where the re-loaded types will have the logger (and also an ImGui instance) uninitialized and run into various problems.
  • If possible I would like to have access to the loaded module, so if necessary I could find my own API's there and call them as required.
• Provide a way to replace Compiler and Filesystem watcher objects using interfaces. A nice chunk of the project is already nicely built around interfaces. Having additional interfaces for it would be great.
  • Not the most important feature, but if it's behind an interface giving the option is always nice. Even if just for logging by wrapping the original object.
• Provide something like a "ICompilerOptionsResolver" that could return the options just before compilation.
  • I've not dept-dive into how RCC++ builds the final DLL, but one thing I was hoping to do is to actually just read a "CompileCommands.json" into memory, find the file that was requested for building and return options from it.
    • This would help me with the setup I have based on Conan. It happens quite often for me to add or move dependencies by just moving a few lines, refresh the projects and it's done
    • I've yet to find a good way to deal also with the linking part.

Back to the RCC++ breaking changes mentioned in #139

Well, it's not like I need to introduce breaking changes. In most cases giving access, for example, to the loaded Module, can be done by just extending the interface.

I would like a leaner version of RCC++ and maybe request a few features here and there when that will be ongoing.
In the meantime, I'll work withing the existing boundaries, and if possible, provide a few PR that you might or might not like to take. In the end, maybe you could base the next version on an idea that was not idea for this version!

Cheers!