Caspian Baska
Caspian Baska
Thanks @SuperPaintman for writing the great library, would you be willing to welcome other contributors to help with maintenance?
Having a `shards release` command makes sense to me. As `shards` uses semver and the reference is pulled from version control tags, it's a pretty limited surface to manage... but...
Could you please run `crystal tool format`? BTW, this looks incredible!
I got these results against the benchmark from #8324 Note: the benchmark does not test the algorithm against longer strings. [gist here.](https://gist.github.com/caspiano/cb45164876d443410f62b391c622238d) ``` old 404.67 ( 2.47ms) (± 3.54%) 195kB/op...
I'm happy to give it a whack! it might take me a bit but I also have some familiarity with the codebase from a previous PR
I think traversing the shard/app's specs may still be useful for producing a warning if a public method that is exported by the project isn't used (can't be guaranteed that...
In that case, wouldn't you expect that method to have been spec'd? I think it could encourage coverage of the library's public surface. Would it make sense for it to...
This is a desperately needed feature. Without it, basic things like abstracting out a single static value requires the use of the `env` key, which is not supported across all...
@straight-shoota I took heed of discussion in #52. I think having the option to use a commit in addition to other references is useful enough to warrant the script.
What about a JSON RPC api? It would be pretty simple for other languages to implement over websocket