HaxeFoundation / HaxeFoundation/haxe
Type parameter constraints are not validated when checking @:coreApi compliance
Open
bug
- Dominant language
- Haxe
- Stars
- 6.9k
- Forks
- 715
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 11
Description
As discovered in #7189, apparently when validating `@:coreApi` we don't check that type parameter constraints are the same, so for example before b865f06c7fbcaf2281fb55f6ed24ac642489e998 it was possible to call `Type.enumEq` on non-enum values, even though the `@:coreApi` class strictly defines the constraint.
Contributor guide
Assessment
This issue has not been assessed yet.