First time I've heard of so_reuseport, which is interesting. The important parts of the setup seem to be that + peering; is peering built-in to PgBouncer and simple to set up?
I've been learning the basics of using Z3 by creating a solver for the daily puzzle game Clues By Sam (very fun game; https://cluesbysam.com/). Repo is https://github.com/DylanSp/clues-by-sam-solver. It uses Playwright to read clues and submit guesses; I've got it working for all 50 puzzles in puzzle pack 1.
Echoing the others who say they can't understand the bug/difference; only thing I can think of is that the input string needed the escape sequence for a newline in it? So the correct code would be written as
Thanks for the explanation - I was deeply confused by this article's premise. I've never worked with Next.js or Astro, so I didn't have the background.
I'm working on an app for easily conducting and organizing evals for LLM-powered applications. The core idea is making it easy for domain experts to review examples of interactions and tests with synthetic data, as well as tracking an application's evaluated performance over time as changes get made.
It's not a perfect situation, but C# has some dedicated collection classes for concurrent use - https://learn.microsoft.com/en-us/dotnet/api/system.collecti.... There's still some footguns possible, but knowing "I should use these collections instead of the regular versions" is less error-prone than needing to take/release locks at every single use site.
This is definitely a big factor. I've found one compiler bug, but it was in a feature that had been added all of two months earlier (optional chaining in Typescript 3.7).
The same author has full articles on Jedi Knight [1] and X-Wing/TIE Fighter. [2]. If you go through his archives [3], he's also written a lot about LucasArts' adventure games; I think the first posts that talk about them are the three "A New Force in Games" posts.
Take a look at the links and sources mentioned in his retrospective on the Sparta series: https://acoup.blog/2022/08/19/collections-this-isnt-sparta-r.... Devereaux mentions some different approaches that modern historians take towards Sparta, particularly Steven Hodkinson's arguments that Sparta was more typical and less unusual compared to the other Greek poleis; following up on that work would probably be a useful counterpoint.
It sounds like the indexing time/complexity is increased a lot by the amount of detailed data they're storing. They mention determining which `using` statement is used to resolve each symbol reference in C++ source, to enable dead code detection; that's going to require some sophisticated analysis.
Case 1 is definitely addressed by the Polonius-related work. There's a post [1] on the official Rust blog from 2023 about that, and this post [2] from Niko Matsakis' blog in June 2024 mentions that they were making progress on it, though the timeline has stretched out.