Haxe 4 changes, part 2 #387
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Gama11
reviewed
Apr 18, 2019
Gama11
reviewed
Apr 18, 2019
Gama11
reviewed
Apr 18, 2019
Gama11
reviewed
Apr 18, 2019
|
|
||
| \paragraph{Default Static Extension} | ||
|
|
||
| It is also possible to always enable particular static extensions for a given type, by annotating the type with the \expr{@:using(args...)} metadata. The arguments are the full dot paths of static extension classes that will be applied on the type: |
There was a problem hiding this comment.
This implies that @:using works for every type, while it seems to basically only work for enums and classes at the moment...
HaxeFoundation/haxe#8022
HaxeFoundation/haxe#7930
HaxeFoundation/haxe#7859
There was a problem hiding this comment.
I guess we'll leave this as-is for now :)
Gama11
reviewed
Apr 18, 2019
Simn
reviewed
Apr 19, 2019
|
|
||
| A string in Haxe code represents a valid sequence of Unicode codepoints. Due to differing internal representations of strings across targets, only the basic multilingual plane (BMP) is supported consistently: every BMP Unicode codepoint corresponds to exactly one string character. | ||
|
|
||
| On some targets, the internal representation is UTF-16, which means that non-BMP Unicode codepoints are represented using surrogate pairs. It is still possible to work with strings on these targets without having to manually decode surrogate pairs by using the \href{https://api.haxe.org/v/development/haxe/iterators/StringIteratorUnicode.html}{Unicode iterators API} provided in the standard library. |
There was a problem hiding this comment.
I thought that we wanted to remove StringIteratorUnicode in favor of Utf8.iterate, but I'm not sure. Have to keep that in mind though.
There was a problem hiding this comment.
|
@RealyUniqueName: Can you check the null-safety section? |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Continuing #383 for an easier review process.
Syntax
XMLMarkup literalsStdlib
implements Dynamiconexterns onlysys.threadhaxe.iteratorsCompiler defines
warn_var_shadowingupdate the list of defines(Reorganise compiler defines #389)Compiler features
Target changes
*.Syntaxclasses to replaceuntyped __{js,php,...}__ES6 generation via(already documented)-D js-es=6Map,Set,Date...js.lib--php-{prefix,front,lib}changed to-D php-*=-D lua-vanillaevaltarget ?@:persistent(replacingregisterModuleReuseCallandonMacroContextReused)External libraries
hx3compathaxe.remotinghaxe.web.Requesthaxe.unitrecord-macrosOther changes
--long-argumentnow.<platform>.hxfiles@:usingdisplay+ IDE integration,vshaxe?enum values without arguments as default function argument values(Constants page / Literals page #386 + Enum case without arguments cannot be used in inline final haxe#8187)