Tell the user about unclean caches
I received a complaint from and non-developer admin that config:set should clean the cache afterwards.
I don't think automatically flushing the cache is a good idea, but it would improve usability to show a warning about unclean caches, just as the magento backend does.
What do you think?
I would also say that always cleaning cache is not good for config:set. For example with extensions like hs:ccd:import which runs config:set internally, it would always clean the cache - while this would be only useful once and afterwards.
However I don't remember that Magento was showing me a warning about unclean caches whenever I was submitting a configuration form in the adminhtml. Where is that message when storing a setting?
And I can understand that cache invalidation is nothing easy to do. A hint might point someone into the right direction. I could test it with hs:ccd as I know it uses that command internally.