datahike

https://datahike.io/, Join the conversation at https://discord.com/invite/kEBzMvb, history for this channel is available at https://clojurians.zulipchat.com/#narrow/stream/180378-slack-archive/topic/datahike
jrwdunham 2020-06-08T04:40:15.358200Z

@grischoun thanks for the details. I'm looking forward to digging deeper into that project.

Ben Sless 2020-06-08T16:40:06.359900Z

@whilo apologies for spamming you here. I amended the latest commit, not sure if you've seen it.

Ben Sless 2020-06-08T16:40:16.360Z

https://github.com/lambdaforge/datalog-parser/pull/11

1
whilo 2020-06-08T23:55:44.361300Z

@ben.sless Thank you, merged and released as 0.1.7 on clojars. That parsing speed up should be partially good for clj-kondo @borkdude.

❤️ 2
🙏 1
borkdude 2020-06-09T07:20:58.361900Z

PR for clj-kondo welcome!

whilo 2020-06-09T20:41:21.366200Z

@borkdude I am just letting you now, but I assume you regularly bump deps anyway. I already have considerable management overhead and would prefer not to go through more, but I also understand that it is the same for you and you need to keep track of all the open ends. If you think it is good to do a PR, I will do it.

borkdude 2020-06-09T20:44:04.367100Z

> I assume you regularly bump deps anyway I actually don't do that automatically, unless there is a new feature or bugfix that I want. I'm not using datalog myself at the moment, so it's best if people who are actively using that part of clj-kondo do the PR with a reason/summary of what is new, so I can mention that in the release notes

borkdude 2020-06-09T20:45:25.367300Z

I don't see anything written here: https://github.com/lambdaforge/datalog-parser/blob/master/CHANGELOG.md

borkdude 2020-06-09T21:10:24.367700Z

eventually the dep will be bumped though. If there is a specific reason to do it right now I'd just like to know.

borkdude 2020-06-11T21:38:33.370800Z

Bumped the deps 🙂