Skip to content

Conversation

@ninjamuffin99
Copy link

I believe this fixes it complaining about using the @:extern metadata! I've checked it against the previous outputs and it looks like it's the same!

Comment on lines -124 to +123
field.meta.push({
name: ":extern",
pos: U.pos()
});
Context.getLocalClass().get().isExtern = true;

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this will change the behavior... 🤔

The removed lines add extern metadata to variables that should finally be wiped, like foo:IVec3 which will be decomposed into fooX, fooY, and fooZ.
On the other hand I think Context.getLocalClass().get() returns the current class that is to be built, so setting it extern may wipe the entire class, but is not working somehow if it isn't causing compiler errors?

Haxe is complaining about the metadata because the metadata @:extern has been promoted into an attribute extern, so adding the attribute properly may be the right way. I need to look into it.

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.

2 participants