The syscall package

We observe a consistent trend: the vast majority of functionalities we require are readily accessible within the standard library, a testament to its comprehensiveness and utility. However, there is a notable exception in this pattern – the syscall package.

The package has been a foundation for interfacing with system calls and constants across various architectures and operating systems. However, over time, several issues have emerged that led to its deprecation:

• Bloat: Who doesn’t love a package that grows without bounds? With definitions for just about every system call and constant you could (or couldn’t) think of, syscall was like that overstuffed closet you promise to clean out... someday.
• Testing limitations: A significant portion of the package lacks explicit tests. Moreover, cross-platform testing is unfeasible due to the package’s design.
• Curation challenges: The package was reminiscent of the Wild West when...