So currently the doc for EReg.matched says this:

The index n corresponds to the n-th set of parentheses in the pattern
of this EReg. If no such sub-group exists, the result is unspecified.

But it's not immediately clear what "no such sub-group exists" means exactly. I assume it means that the group was not defined in the regex. But it's a bit confusing in case the group was define

Expose raytracing render-path in Armory and document implementation details.

Call FlxG.gamepads.firstActive.firstJustPressedID() with an xbox controller plugged in. It will always return GUIDE when nothing is pressed.

The reason is simply that the the raw ID for the guide button on xbox controllers is -1, which is also the id flixel uses for NONE. We hit https://github.com/HaxeFlixel/flixel/blob/master/flixel/input/gamepad/mappings/XInputMapping.hx#L34 when doing getID(

The author of the project is an expert programmer but a color science dilettante. If you have ever read a color science book from cover to cover, you are qualified to rewrite all website to make sure terminology is correct.

The website also links to an old blog post of mine:
https://www.boronine.com/2012/03/26/Color-Spaces-for-Human-Beings/

It would be valuable to integrate the information

Something I found hidden in the hl docs that didn't show in the API docs:

https://github.com/HaxeFoundation/haxe/blob/72ef1d389e1f1ae3fdbf8a9f6bf76d39774db23b/std/sys/thread/Tls.hx#L32-L33

I'm guessing there should be some hl_add_root calls in thread.c.

Commit in question

#574 -> Updated Scene to return empty containers

Comment

I feel like it makes sense to use some form of memoization
If we're querying the existing entity types and someone attempts to get a qualifying Entity, then cache the result as empty
much like adding an entity of that type, but with no actual allocation other than the array

Ben Morris's suggestion:

Would be nice to restrict shape size min/max per step in the options. This way I would start with huge shapes in the beginning, and progressively in later stages reduce the size when more details should be added.

( Would work great with the focus areas from #3 )

I try to compile a wasm via lime test emscripten -webassembly but I get this error following.
How can i fix it and compile it?

Compiling group: hxcpp_std
emcc -c -fvisibility=hidden -O1 -fpic -fPIC -DEMSCRIPTEN -Wno-overflow -Wno-parentheses -Wno-unknown-warning-option -Wno-null-dereference -Wno-unused-value -Wno-format-extra-args -Wno-bool-conversion -Wno-warn-absolute-paths -DSTATIC_

Some messages by the IRC bot currently don't include the job ID. This makes it harder to reconstruct what a job was doing exactly, e.g. when it needs to be requeued, since you can't just grep all lines relevant to a particular job from the IRC logs.

This requires changes in the pipeline code, see details in my failed attempt at #328.

It seems that API documentation linked by README hasn't been updated for a while. It says that UIEvent is in haxe.ui.core but in the code for 1.0.4 it has been moved to haxe.ui.events.

I mean the thing you get when pressing Ctrl+q.

Right now you only get a short description for the class or method with no formatting at best. Explaining a method's parameters, too, would be a nice addition, for example. I know that you can bring those up with Ctrl+p, but that doesn't

Gfx.fullscreen is good for assigning fullscreen values, but doesn't respond (on OSX native builds at least) to the user manually going into fullscreen mode.

I read that the JVM target, "gets rid of issues with incompatibility between Haxe and Java type parameters."

It would be best if any compatibility issues with Java and differences between the two targets were detailed in section 12.8.

README should be added to the root level of haxelib package.
And, prehaps, add following line in "How to use" section:

haxelib run as3hx test/ out/

https://groups.google.com/d/msg/haxelang/qdFUlNYKpbE/s_FsuROIAwAJ

When readme is rendered on github anchor links like [Installation instructions](#installation-instructios) allows to reference any header in that same readme.
I think haxelib website should reproduce this behavior.