Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Possible bug in @:autoBuild meta order #11194

Open
filt3rek opened this issue Apr 30, 2023 · 1 comment · May be fixed by #11634
Open

Possible bug in @:autoBuild meta order #11194

filt3rek opened this issue Apr 30, 2023 · 1 comment · May be fixed by #11634

Comments

@filt3rek
Copy link
Contributor

Hej,

Idk if it's a bug or it is intentional, or none of these, maybe it's "just like that" ?

class Macro {
	public static function ab(n:Int) {
		trace("ok"+n);
		return null;
	}
}

Traces :

Macro.hx:3: ok2
Macro.hx:3: ok1

With that :

@:autoBuild(Macro.ab(1))
@:autoBuild(Macro.ab(2))
interface IFoo {}
class A implements IFoo {}

And traces :

Macro.hx:3: ok1
Macro.hx:3: ok2

With that :

@:build(Macro.ab(1))
@:build(Macro.ab(2))
class A{}

I mean the order is not the same, and Idk if it's intentional. If not, could it be possible to "uniformize" (the same between @:build and @:autoBuild metas) please ?
@Simn
Copy link
Member

Simn commented Apr 30, 2023

Hmm yeah, I'd expect that to at least follow lexical order here.

@skial skial mentioned this issue May 3, 2023
Closed
1 task
@kLabz kLabz linked a pull request Jul 19, 2024 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Macro build order HaxeFoundation/haxe
2 participants
@Simn @filt3rek