...instead of [-10;10]. The reason for [-10;10] is to get good-looking docs, but that should be a compile-time option. Once 3.0 is released we can't change it anymore, so we'd rather switch now to a natural choice, and the only natural choice is to use the whole integer range. One should first implement ei_random() manually for each integer type; and then implement ei_random(a,b) from it.
Indeed, beta3 blocker. Keep the old behavior when building the docs.
Should be fixed now. Now random<integer types> spans over 0..RAND_MAX, or -RAND_MAX/2..RAND_MAX/2 for signed types, or the most significant bits for smaller integer types.
-- GitLab Migration Automatic Message -- This bug has been migrated to gitlab.com's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.com/libeigen/eigen/issues/45.