Fix for haxe 3.3 macro execution order #93
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #91 and luxeengine/alpha#383
Probably it's a haxe bug that
Context.getType
can't access other types during building, even if types aren't forming cyclic references. Instead i'm building type path to be defined directly, using simple string splitting. This avoids assertion failure, thrown by compiler otherwise. Also i'm using@:eager
meta to force building types.Another change is related to a new behaviour of
switch
expression: case values are no longer allowed to be writable variables. Even though it should not directly impact snow, it prevents mint from compiling with an error in keyboard translation code.