microsoft / microsoft/ifc-spec
Allow arbitrary custom attributes.
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 94
- Forks
- 11
- Avg merge
- 1d 29m
- Merged PRs (30d)
- 2
Description
Ifc-spec defines a comprehensive definition of attributes, but MSVC discard custom or unrecognized attributes.
This would be incredibly useful for tools that relies on IFC for it's C++ introspection, for example:
- static code analysis tools being able to opt out of false positives.
- Runtime reflection where some fields are can be optionally be ignored.
Contributor guide
No contributing guide indexed for this repository
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
Start with the IFC specification's definition of attributes and the sections describing how MSVC handles unrecognized attributes. Determine how arbitrary custom attributes should be represented and preserved for static analysis and runtime reflection, then document precise acceptance criteria for supported behavior; no implementation files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100