i’m running into some speed bumps while writing an expectimax solver for 2048

it’s taking like 2 full seconds to calculate a move from a expectimax search of depth 4

i’m sure there are some inefficiencies in my game logic (and i’m rewriting that as we speak to include precomputed lookup tables), but i’m wondering if anyone has some good ideas/suggestions

https://github.com/xtrntr/cljs-2048

What do you use for E2E testing?

clj-webdriver

hello guys

really new to clojure and i'm finding Boot to be a real challenge

I'm trying to set up my repl in build.boot to bind to a specific port yet not tied to a ip but to localhost for remote purposes. I tried setting the task-options! repl { :host 0.0.0.0 :port 9000} but nrepl seems to still get bound to 127.0.0.1. What do I do to get remote repl?

@val_waeselynck: It looks to me a bit abandoned at the first sight, am I wrong?

@novakboskov i just think it's stable really

@dominicm: I'm getting some intermittent value printing 😞

I have no idea if its the recent change but it's on the list of suspects

Yeah, course. We'll have to figure it out, is this for the streaming feature of cider?

Not sure at all going to track the value right now

actually being able to trace a value through the stack would be so incredibly helpful eh... again another reason for comprehensive logging and possibly a central event dispatch bus

@dominicm: it is not your patch at all

so no worries there

client side eval is returning nil intermittently

for a javascript object

OMG finally bitten by the multiple repl dispatch!!!

one window didn't have the dom element and the other did

@bhauman: Youch. 😞

yeah this is on the list

@dnolen: I was chatting with @alexmiller about making a clojure.spec.gen/let macro for more conveniently defining generators for spec. It's a really simple macro: https://gist.github.com/ef92987c8160a796b62c95e207ee0ad4 Should I go ahead and try and make a patch for cljs.spec.impl.gen? Also, it's easy to coerce variables being bound in this let to generators... should I write that too or is that too much magic?

@xcthulhu: only interested in stuff like that if already implemented in Clojure first

that stuff should be copy paste

Alright, I'll do it in Clojure, see if people want it in core, and then bother you if it works out.