I've refactored the code of the library to make sure that the compiler identifies the list and the operation types being from Core.List, recompiled, opam pinned the project. But I keep getting blowups. I've executed the code in gdb, and gotten a backtrace with the stack overflow and I can see that it's still going to List.map.

So I'm thinking it has to be one of a few errors:

I've fixed it, but it's linking against a different, older version of the library.

* Problem with this is, the makefile generates ocamlfind calls, and those resolve the package correctly. I've check the file dates, removed the packages and readded them a multi-tude of times. Unless there's some invisible /usr/local compiler selection over the opam stuff despite it being specifically pointed there, I don't see how this could be. But I could be wrong.

I've fixed the library some, but it some how resolves to a Pervasives type that's not tail recursive somewhere in the library that I missed.

* I still don't see how this could be. I'm looking in the gdb backtrace, and I can see where it flows from my code into the library-the library. I've tracked the naming convention down to the exact function definition and checked via Emacs Merlin that it's the type it should be.

I've fixed the library correctly, but somehow a mismatch between pervasives and Core definitions causes some fallback to the pervasives via some kind of invisible typing rules or language specifics that I don't know about.

* Maybe, but wouldn't the compiler complain if it expected a Core.Std.List.t and got a list instead?