Pierre Krieger

Let's keep this open in fact. There are other limits that aren't checked yet: ``` uint32_t maxTessellationGenerationLevel; uint32_t maxTessellationPatchSize; uint32_t maxTessellationControlPerVertexInputComponents; uint32_t maxTessellationControlPerVertexOutputComponents; uint32_t maxTessellationControlPerPatchOutputComponents; uint32_t maxTessellationControlTotalOutputComponents; uint32_t maxTessellationEvaluationInputComponents; uint32_t...

Another desired feature is to have some sort of round robin of queues, so that the user can easily dispatch multiple tasks to multiple queues. It would of course be...

Yeah I guess recompiling Rust at runtime would be too hard anyway. If the link between the GPU code and CPU is put in its own module, and if Rust...

Memory safety is not irrelevant. If you perform an out of bounds access in your shader, you will get a graphics reset (cc #356). Thread safety is not irrelevant, because...

I'm also wondering how you would actually handle an OOM error when submitting.

Note that Substrate doesn't support `/tls/ws`. We can't do anything before it does.

This issue is quite complicated. Switching from optimistic to all-forks syncing is relatively easy, but switching back from all-forks syncing to optimistic is an extremely hard problem as we lose...

I've added a test case just in case (https://github.com/Tomaka17/luawrapper/commit/224168bae24277b83f7f4c3a2a9809236219206e) but it works. I have also tested this on the previous version and it works too. The problem may come from...

Yes you can (though it is not a very elegant syntax)

I was thinking more something like: ``` lua.writeFunction("Vector2f", "new", [](auto... params) { return Vector2f{params...}; }); ``` `params` would automatically be of the types that were provided by Lua core, instead...