premake / premake/premake-core
want filter more complete.
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 654
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 13
Description
So, I've been kind of looking at getting this working:
workspace 'foo'
rtti 'on'
project 'bar'
filter { 'rtti:on' }
<dosomething here>
The easy thing is to just add rtti and the other things I want to the filter context, but that is obviously kind of arbitrary... So I was wondering if anyone has a decent idea on how to generalize this to all api's?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by tracing how the existing rtti setting is represented and how filter contexts consume settings, using the workspace/project example as the entry point; done would require an agreed general mechanism for exposing settings to filters, with behavior validated for rtti and other APIs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100