
jsonstein@masto.deoan.org ("Jeff Sonstein") wrote:
oh yay, I think I *finally* figured out how to properly integrate native threading into my seekrit project. a big chunk o’latency unavoidably built into one function (talking to someone else’s server) was pushing it into synchronous request-handling. native threading & ‘vibe.d futures’ was the solution.
I know I am on the right track to properly ‘grokking the problem’ when my code begins not just working right (according to logging), but also getting smaller and simpler and faster.