HaxeFlixel / HaxeFlixel/flixel
Raise minimum haxe version from 4.2.5 to 4.3.7
Open
Nobody has claimed this yet.
Breaking Change
CI
Code Style / Cleanup
Structure
- Dominant language
- Haxe
- Stars
- 2.2k
- Forks
- 522
- Avg merge
- 34m
- Merged PRs (30d)
- 1
Description
Continuing off of #2774. It's still far too early to switch to 4.3 as a minimum target, it hasn't even been a month and adoption for 4.3 will be notably slower than 4.2 since there are so many deprecation warnings and odd errors that have turned up, notably #2780
- Use self in abstracts that reference themself
Nice, but has no actual benefit to devs - Have strict nullsafety without unit test errors
- Static final local points rather than pooled points per intance
Significant memory gains, IMO
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
Review the context in #2774 and the compatibility concerns in #2780 before locating the repository's current minimum Haxe version declaration. Check the referenced FlxTilemap test and FlxCamera.hx change for affected-version assumptions; done means the project consistently requires Haxe 4.3.7 and the relevant tests or checks still pass.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, game-dev
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100