Dario Teixeira

Yeah, the compiler is complaining that the type variable is weakly polymorphic. This is not really a problem: you can either add a type annotation, or -- most likely --...

@Giels: can you provide a real world example where this is a problem? (Also, in case you haven't done so already, please read [this](https://realworldocaml.org/v1/en/html/imperative-programming-1.html#side-effects-and-weak-polymorphism) chapter of Real World OCaml).

@Drup: You're right, there's a chance users may bump into the value restriction, in which case marking the type as covariant would help. I still wonder if there's any real...

The case of the extra type variable is where PG'OCaml's convoluted history rears its ugly head. I didn't write that particular code, and I can only speculate about the original...

Hmm, I've never used the setter/getter functions for private data, but I cannot exclude the possibility that some people are using them. I'll raise the issue on the mailing-list, because...

You do have Postgresql running and configured correctly, right?

Note that the most reliable solution is to always explicitly provide the `unix_domain_socket_dir` parameter of the `connect` function. The default value being set at compile time with some Makefile magic...

I agree -- this would be a cool feature. I don't have much time to muck around with Camlp4 at the moment, though. I suggest we keep this ticket open...

Incidentally, the behaviour of the PCRE library is more useful in practice, though also a bit quirky: for separators at the beginning of a string it behaves like my proposal...

Yeah, consider it a low-priority feature that you may bump into higher priority if someone actually complains about Eliom6... :-)