> In short: your source code is stored in plaintext for the minimum time feasible to be able to process your request. After that, it is discarded and is inaccessible. In very rare cases your code may be kept for a little longer (at most a week) to help debug issues in Compiler Explorer.
> All submitted binaries are saved and made available to any of the authors of the tools used so they may improve their decompilers. If you're such an author who would like access, let us know!.
We were planning on eventually making it into a website and doing a leaderboard.
The program works by having agents that write to stdout and a game that reads from stdin. That way we can kinda avoid some of the security issues around running untrusted code.
Still has a lot of work to be done before it's ready to simulate battleship :)
Definitely in a real game against a human you would want to adjust the weighting based on historical game data.
When I'm playing games against my friends, I treat the solver like an advisor. So sometimes I ignore what the solver says and instead choose from only edge squares.
Author here. Yeah that graphic is a little confusing.
Since we have a 3x3 area of squares that are already accounted for by the current hit, we only focus on expanding that 3x3 area into a 3x4 or 4x3 area by shooting adjacent squares.
We're expanding the 3x3 to 4x3, so we only focus on the delta between the 3x3 and 4x3 area (hence highlighting the edges of the 3x3 area). Once we decide which direction would result in the most potential ships being eliminated, we shoot in that direction.