Niklas Fiekas

Fixed by dereferencing the pointer only for `f(unsafe { &mut *cur })`. To be honest, I don't understand how std gets away with not doing it like that.

This would indeed be really helpful. Coming from Python I had `class:` somewhere in my code and had no idea that could be related to `Unexpected 'TERMINATOR'`.

Thanks for reporting. I am not actively maintaining this repository, because it is superceded by https://github.com/niklasf/stockfish.wasm in modern browsers, but I will merge proposed fixes.

With `ZobristHash` from #40 we now have a useful building block. Nonetheless I am hesitating on this one, because it requires adding a representation for games (rather than just position),...

I think the first suggestion (going with `Italian Game: Giuoco Piano`) ist most consistent. Do you want to submit a pull request?

Unfortunately I don't think that's a realistic goal for our APIs, even if we artificially hold back responses.

That would work, but plenty of the stricter rate limits are in lila.

Thanks, that's a useful feature. My concern is that it has some overhead even when unused. It would be great to have a (type-safe) way to opt-in. Not sure how...

I am also not sure about the design. I feel like enabling hashing should probably not be a runtime decision, i.e. not an optional argument, because the developer will know...

> any areas that we could improve shakmaty? My thought being it could net-out if we add zobrist. No concrete ideas, but that would be awesome. I'd probably be greedy,...