Stéphane Magnenat
Stéphane Magnenat
Please do not close, it is still a useful feature to consider...
A new release would be needed as in its current state, the released diesel-geography indirectly depends on a yanked package. This was fixed by PR #7, but without a release...
Thank you for your answer! I am using Webpack actually. I also tried the option you propose before posting the issue, but then Webpack crashed at startup due to the...
I am positive I used the very-up-to-date version by then `loader.js` was in the npm bundle. I did not find time to create a minimal reproducible test case, because as...
If I am not mistaken, a partial version of this feature, only sampler arrays (Vulkan extension `shaderSampledImageArrayDynamicIndexing`) is supported on 92% of Android devices listed on gpuinfo ([supported](http://vulkan.gpuinfo.org/listreports.php?platform=android&feature=shaderSampledImageArrayDynamicIndexing), [not supported](http://vulkan.gpuinfo.org/listreports.php?platform=android&feature=shaderSampledImageArrayDynamicIndexing&option=not))....
Any status update on this PR? The bug it solves is likely to hit pretty much everyone using Rust with GPU on the web (through Bevy or something else), so...
A note about that. We had a similar discussion in [aseba](https://github.com/aseba-community/aseba). Beside breaking the history, automatic formatting also breaks some special formatting done on purpose by the programmer (for example...
[This file](https://github.com/aseba-community/aseba/blob/master/.clang-format) might be a useful starting point for the formatting rules, as both aseba and libpointmatcher kind of follow "my" style.
That's true, a tree is indeed not really needed!
Actually, there were 4 errors, now 3 left: ``` 112:23 error Missing space before function parentheses 113:24 error Expected '!==' and instead saw '!=' 113:27 error Strings must use singlequote...