HaxeFoundation / HaxeFoundation/haxe
`@:forward(names)` vs. completion
Open
feature-ide
- Dominant language
- Haxe
- Stars
- 6.9k
- Forks
- 715
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 11
Description
```haxe
class C {
public function new() {}
public function forwarded() {}
public function notForwarded() {}
}
@:forward("forwarded")
abstract A(C) {
public function new() {
this = new C();
}
}
function main() {
final a = new A();
a.
}
```
Compilation correctly fails if I try to use `notForwarded` there, but completion thinks that's fine.
Contributor guide
Research direction
Start with the Haxe reproduction in the issue and trace the completion path for an abstract using @:forward(names). Compare its suggestions with compiler acceptance; done when completion excludes notForwarded while retaining forwarded.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100