mighdoll
mighdoll
@ctrlplusb would you or another committer familiar with easy-peasy take a peek at [undo-peasy](https://github.com/mighdoll/undo-peasy)? I’ve just published a 0.2.2 version with better performance and more comments. When it's good to...
Thanks for the nifty plugin! We've just started using sbt-pack but ran into a problem mixing sbt-pack and file dependencies. Join the conversation here https://github.com/sbt/sbt/issues/1152 ?
Please post a software license (BSD, apache , etc.) with the source code and in the POM
When following standard conventions, users put .scala files in the root of the project directory in sbt. However, sbt-eclipse doesn't add a .classpath entry for these .scala files in the...
I added a dependency with a classifier, and it seems to confuse sbteclipse. Example: ``` "com.github.fommil.netlib" % "netlib-native_system-linux-x86_64" % "1.1" classifier "natives" ``` while sbt correctly downloads the correct jar...
Hey, wanted to introduce our effort over in the [wgsl-tooling-wg](https://github.com/wgsl-tooling-wg/wesl-spec) to extend WGSL with community tooling. The idea is to extend WGSL to support features like `import` from local files...
For WGSL in an npm/cargo package, static group and binding indices aren't a good idea. The indices need to be chosen by the application (preferably the application host code), not...
## Description `UnionToIntersection` fails in some cases. I posted about an example [failure](https://mighdoll.dev/blog/typescript-tricks-combining-records/#recovering-record-types-from-record-intersections), and later about a [fix](https://mighdoll.dev/blog/modern-typescript-intersection/) to `UnionToIntersection`. ## Steps to Reproduce [Playground link]( https://www.typescriptlang.org/play/?#code/C4TwDgpgBAggShAxgewE4BMoF4oJRgHgEMA7EAGilJAD4BuAKFEigDUJUBLAMxAIBUoEAB7AIJdAGdYeNOhrYo-OlCgB6NVG5FOAGyjBkB8EgAWSANZQeS69JLJgVXEjkMRYNE+bQAqiU5kEn5kAEkSMVRJJGBAkgJfBRwACl8hUXEpKjIGAH4oZIsALihfAEpsBQA3ZE50BhKSCCqOCpExCWlCks4Sbg4oUIqsatr61XzQhlVG5o5GBg0DU05pAHc0C0kmEygAYSDEVAgxcMjoxCccdi5eBICgkLOOC9igggBvKhKARgBfKAAHygXwARiUAEx-Gj0BiLTTAFbSdDICCSEgAcicG1QFgAdAUAOqmEC5MrwqAAAQ4qDQ0ghAGYACxMnYsAAKRFQRAAts8ojECDB0h0svBXBgkmwODw+P44k8Ii8YnEhTCVHClhjev1UIMRZlpL4MVpOMI0dZgGzoPzXnFCZxEQBRDKdBJS6aqAppdqG7IgKD5T1egrFUrDUZ1KCzFqoNqurLBr3dax9AahA2dcOVKA1KNBkMZmPza1QTncvlKgWXCFCzNi2SSxQ3WUEW0qoIO50JyRq+hQUv8NHACGKcu89s1z7fKD-IEgqDgqBQ-sUr0APVyDCAA) ## Expected behavior...
It'd be nice to iterate on my package and see how the docs look w/o having to publish to npm with each change.. Is there a way to try a...