Skip to content

[typer] allow int/i64 literals as haxe.Int64 default argument values#12923

Draft
kLabz wants to merge 1 commit into
developmentfrom
int64_default_arg_value
Draft

[typer] allow int/i64 literals as haxe.Int64 default argument values#12923
kLabz wants to merge 1 commit into
developmentfrom
int64_default_arg_value

Conversation

@kLabz

@kLabz kLabz commented Jun 2, 2026

Copy link
Copy Markdown
Contributor

Int64 values are never compile-time constants (they are built through Int64.make), so they were rejected as default argument values. Accept an int or i64 literal default for a haxe.Int64 argument and let each generator materialize the constant expression on the not-passed path (no Null<> boxing, so no overhead on value-type targets like hl).

Not supported on cpp yet (default_value_string can't render an Int64), so it errors there for now.

Int64 values are never compile-time constants (they are built through
Int64.make), so they were rejected as default argument values. Accept an
int or i64 literal default for a haxe.Int64 argument and let each generator
materialize the constant expression on the not-passed path (no Null<>
boxing, so no overhead on value-type targets like hl).

Not supported on cpp yet (default_value_string can't render an Int64), so
it errors there for now.
@skial skial mentioned this pull request Jun 4, 2026
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant