Thanks David! I'll try to fix that in the next few days.
On Oct 5, 5:57 am, David Nolen wrote:
> On Fri, Oct 5, 2012 at 8:51 AM, nchurch wrote:
> > Hmm! Then I must have hit the limit for how many arguments I can put
> > in an arglist, there in fresh: (i.e. (fresh [~@positions]). I had no
> >
On Fri, Oct 5, 2012 at 8:51 AM, nchurch wrote:
> Hmm! Then I must have hit the limit for how many arguments I can put
> in an arglist, there in fresh: (i.e. (fresh [~@positions]). I had no
> idea there \was a limit. Can't see any way around that at the
> moment. I never dreamed I'd try to put
Hmm! Then I must have hit the limit for how many arguments I can put
in an arglist, there in fresh: (i.e. (fresh [~@positions]). I had no
idea there \was a limit. Can't see any way around that at the
moment. I never dreamed I'd try to put > 256 arguments in a
function
On Oct 5, 5:46 am, Da
On Fri, Oct 5, 2012 at 8:42 AM, nchurch wrote:
> CompilerException java.lang.ClassFormatError: Too many arguments in
> method signature in class file go/core
> $eval2878$fn__2881$fn__2882$_inc__2883$fn__2884$_inc__2885$fn__2890,
> compiling:(NO_SOURCE_PATH:1)
>
Yeah that's not core.logic relate
I realized what the latter issue is: I forgot to relationalize
"opposite". It turns out not to matter when you're checking for
alive, but it does matter checking for dead for some reason. See the
new push.
The board size limitation issue has a \very odd error message that
doesn't seem to come fr
On Fri, Oct 5, 2012 at 1:53 AM, nchurch wrote:
> Here's a Go solver
>
> code:
> https://github.com/nchurch/go/blob/master/src/go/core.clj
>
> README:
> https://github.com/nchurch/go
Neat!
> There are some issues that I'd like to get input on. For one thing,
> I've used mutual recursion (
Must say, you sir have written some very interesting code there!
Regards,
BG
On Thu, Oct 4, 2012 at 10:53 PM, nchurch wrote:
> Here's a Go solver
>
> code:
> https://github.com/nchurch/go/blob/master/src/go/core.clj
>
> README:
> https://github.com/nchurch/go
>
> It's a really fun use of cor
Here's a Go solver
code:
https://github.com/nchurch/go/blob/master/src/go/core.clj
README:
https://github.com/nchurch/go
It's a really fun use of core.logic: you can test for pieces being
alive or dead; you can also generate all the boards that make a given
piece alive or dead. See the READ
