there is a single particularity in this proposal, and it could solve something I have been bitten
by some time ago when improving *.random functions in Elixir core.
I couldn't figure out why all tests related to random functions were not working, and that's becuase
when creating Integer.random (a function that never made it to core) I used :random.seed instead
of :rand.seed.
Believe me it took me a while and a lot of head scratches to figure out what was going on.
Having two modules so similar it's a source of confusion, and being this function a critical
function when generating randon values could be a source of security bugs: so I don't think it
would be a bad idea to have a Kernel.seed funcion
On Wed, 21 Sep 2016 21:01:23 +0200
José Valim <
jose....@plataformatec.com.br> wrote:
> We typically avoid only wrapping Erlang functions because in the long term
> we will just end-up duplicating all the efforts already done in the Erlang
> community. For example, even for a simple case such as Kernel.seed, we need
> to document the tuple format, the meaning of exsplus, etc. And unless we
> wrap all the functionality in rand, at some point you will still need to
> use rand directly.
>
> So I would like to propose other initiatives:
>
> * We should continue to focus on better documenting those entry points,
> which we already do in places such as the Getting Started guides
> <
http://elixir-lang.org/getting-started/erlang-libraries.html>. In fact,
> your article is a great exploration of the rand module and, if you send a
> pull request to the guides linking to your article in the rand section, we
> would love to merge it!
>
> * Send a pull request to Erlang/OTP that improves their documentation. For
> example, including an example of using the crypto module for a
> cryptographically secure example would probably be very welcome.
>
> * Send a pull request to Erlang/OTP that adds the functionality you would
> like to see Elixir wrapping.
>
> If you or anyone else need help in contributing to Erlang, please ping me
> any time, either on IRC or by e-mail and I would love to provide guidance.
> Improving Erlang is our responsibility too! :D
>
>
> *José Valim*
> > email to
elixir-lang-co...@googlegroups.com.
> > <
https://groups.google.com/d/msgid/elixir-lang-core/577910ae-2a52-49f4-9e77-670639106a3c%40googlegroups.com?utm_medium=email&utm_source=footer>
> > .