# Generic numeric module, Problem with types

**URL:** <https://discuss.ocaml.org/t/generic-numeric-module-problem-with-types/17797>\
**Category:** Learning\
**Created:** [February 11, 2026, 8:58am UTC](https://discuss.ocaml.org/t/generic-numeric-module-problem-with-types/17797 "2026-02-11T08:58:33Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![Leonidas](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/leonidas/32/4039_2.png) [@Leonidas](https://discuss.ocaml.org/u/Leonidas)\
**Post date:** [February 12, 2026, 10:51am UTC](https://discuss.ocaml.org/t/generic-numeric-module-problem-with-types/17797/9 "2026-02-12T10:51:38Z")

</div>

> [@jbe](#):
>
> I generally sometimes wonder how to be forward compatible with includes and open.

I solve this by not doing `open` of modules unless they have specifically been designed for opening (e.g. `Infix` operator modules for `let*` or `>>=` or something like that) or I specifically want an `include` to override my definitions (e.g. when I backport stdlib functions and want these to be replaced by the Stdlib versions if available).

---

_[View the full topic](https://discuss.ocaml.org/t/generic-numeric-module-problem-with-types/17797)._