Implement new concept with exercise: randomness

[norbs57]

Fixes #2038
Implements concept randomness including an exercise
The exercise was partly ported from the roll-a-die exercise on the C# track

[github-actions]

Dear norbs57

Thank you for contributing to the Go track on Exercism! 💙
You will see some automated feedback below 🤖. It would be great if you can make sure your PR covers those points. This will save your reviewer some time and your change can be merged quicker.

• 📜 The following files usually contain very similar content.

  • concepts/<concept>/about.md
  • concepts/<concept>/introduction.md
  • exercises/concept/<exercise>/.docs/introduction.md

  Please check whether the changes you made to one of these also need to be applied to the others.

• 🧦 If you changed the function signature or the function comment in the exemplar file or the stub file (<exercise>.go), make sure the change is applied to both files.

• ✍️ If your PR is not related to an existing issue (and is not self-explaining like a typo fix), please make sure the description explains why the change you made is necessary.

• 🔤 If your PR fixes an easy to identify typo, if would be great if you could check for that typo in the whole repo. For example, if you found Unicdoe, use "replace all" in your editor (or command line magic) to fix it consistently.

Dear Reviewer/Maintainer

• 📏 Make sure you set the appropriate x:size label for the PR. (This also works after merging, in case you forgot about it.)

• 🔍 Don't be too nit-picky. If the PR is a clear improvement compared to the status quo, it should be approved as clear signal this is good to be merged even if the minor comments you might have are not addressed by the contributor. Further improvement ideas can be captured in issues (if important enough) and implemented via additional PRs.

• 🤔 After reviewing the diff in the "Files changed" section, take a moment to think about whether there are changes missing from the diff. Does something need to be adjusted in other places so the code or content stays consistent?

_{Automated comment created by PR Commenter 🤖.}

[andrerfcsantos]

Thanks for working on this. I really like the introduction to the subject you did, is short, straight to the point and the examples are relevant.

Left some minor comments.

[norbs57]

You may have seen it on https://pkg.go.dev/math/rand

…

On Mon, 28 Mar 2022 at 23:56, André Santos ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In concepts/randomness/about.md <#2139 (comment)>: > +### Caution + +The output produced by package `math/rand` might be easily predictable regardless of how it is seeded. +For random numbers suitable for security-sensitive work, you should use the [`crypto/rand`][cryptorand] package. You are right, thought I've seen this somewhere else, disregard the advice then. — Reply to this email directly, view it on GitHub <#2139 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AG2445JX6JTLYWYUSJGRF3LVCI2IJANCNFSM5RVL5LZA> . You are receiving this because you authored the thread.Message ID: ***@***.***>