HaxeFoundation / HaxeFoundation/haxe
use namespaced metadata for targets
Open
discussion
- Dominant language
- Haxe
- Stars
- 6.9k
- Forks
- 715
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 11
Description
As briefly discussed in Slack, maybe it makes sense to refactor all the target-specific metadata (`@:jsRequire`/`@:cppInclude`/etc.) into namespaced variants (`@:js.require`, `@:cpp.include`). If we go with that, we can slowly deprecate the old ones, making them hidden aliases for the new ones and eventually emitting a deprecation warning.
One question here is what to do with target-specific metadata that is shared between a couple different targets, like `@:expose` for JS and Lua, or `@:functionCode` for C++, C# and Java.
Contributor guide
Assessment
This issue has not been assessed yet.