Add these functions:

• sscanf, scanf, etc.
• strtoll, strtod, strspn (some of them maybe are already there)
• __ctype_b_loc behaves wrong (it does not link always and is made symbolic)
• memchr

If an undefined function has a standard name (like printf), should we check also the prototype to increase the confidence that we really may assume that the function behaves like the standard function?

While going over the Wiki and the markdown files, I ran into a few files that look like they're supposed to show examples and counterexamples of valid/invalid code.

Examples:

• https://github.com/Cognifide/AEM-Rules-for-SonarQube/blob/master/src/main/resources/rules/HTL-11.md
• https://github.com/Cognifide/AEM-Rules-for-SonarQube/blob/master/src/main/resources/rules/AEM-15.md

Please confir

A library shouldn't mess with default source in the rand package. Changing the seed can cause unexpected problems in the main program if it depends on it.

Source: https://github.com/life4/genesis/blob/d2ed89b7efab9db45f2abbeaa7c75a55457a52f7/implementation/slice.go#L47