Always happy to get a patch merged! https://t.co/QYpJDi5YWu. Next SBCL version will launch child processes on Linux much faster now (if running kernel 5.9+ and SBCL is built with a new enough toolchain).
#CommonLisp#AdventOfCode2021 day 6 with #McCLIM. I learned how to put borders between cells in tables today. I think AOC chickened out with their exponential growth, though. Should have made the answer be greater than 2^64, to show why automatic BigInt upgrading is nice.
Inspired by @RainerJoswig using a Lisp Machine for #AdventOfCode, I've decided to do the remainder of mine with #McCLIM to visualize things and get more practice with it. This one's not as cool to look at as the Bingo cards, but I did learn some new things about McCLIM!
@NewLispRepos That got me curious. Looks like https://t.co/1p3CyQ39Cq does it. I don't see a way to specify an oldest creation date. But Gitlab IDs are sequential, so it's probably possible to use id_after instead.
@svetlyak40wt I've had some good experiences using Redis to distribute jobs between background CL workers. Haven't used ZMQ from Common Lisp myself, but have heard good things about the bindings.
@svetlyak40wt It's stored in a file called repo in the project folder. Contains something like (:github :path ".../...") described in the "Repository Description" section of the spec. Only has :github and :gitlab right now. But can easily extend it to other types.
@svetlyak40wt Any chance of providing upstream repo information in the index? I'd love to get a full workflow down that lets you easily hack on dependencies.
@svetlyak40wt Nice, I did a quick test and it seems to work well! To be honest, I'm not really expecting much out of the system version field; use of it seems haphazard at best. License would be cool though (although that can also be hit or miss).