_Before opening a new feature request, please read [Requesting New Features](https://github.com/premake/premake-core/blob/master/CONTRIBUTING.md#requesting-new-features) and consider if this is something [you can contribute](https://github.com/premake/premake-core/blob/master/CONTRIBUTING.md#contributing-a-fix-or-feature) yourself. If this a new request, help us help you by filling in the template below._
A clear and concise description of the problem this new feature is meant to solve, ex. "I'm always frustrated when [...]" or "Add support for this new toolset [...]". Please limit your request to a single feature; create multiple feature requests instead.
**What might be a solution?**
A clear and concise description of what you want to happen. If you are proposing changes to Premake's scripting APIs, provide an example of how your new feature might look when scripted. Use [code blocks](https://help.github.com/en/articles/creating-and-highlighting-code-blocks) to format your examples nicely.
**What other alternatives have you already considered?**
A clear and concise description of any alternative solutions or features you've considered.
**Anything else we should know?**
Add any other context or screenshots about the feature request here.
*(You can now [support Premake on our OpenCollective](https://opencollective.com/premake). Your contributions help us spend more time responding to requests like these!)*
