-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
stdlib: organize the standard library modules (lib
)
#1200
Comments
Some thoughts/comments, which may or may not be entirely related to this issue:
|
Thanks for sharing.
I at least somewhat agree, we can do some of this where it makes sense, which would likely be top level
Strongly disagree, if the canonical import is |
So, some open questions:
|
Great questions.
If used by system, and by others, then putting them under the
Not right now, but maybe something will occur to us in the future as we make these changes and learn from them. Fewer changes in this regard will at least be kinder in terms of git history. |
The
lib
directory, which contains the standard library, is a mess. it's difficult to find the module you're looking for without a "go to definition", or resorting to grepping file names. Instead the top levellib
directory should strive to expose all public modules in a flat fashion, with private and implementation specific bits hidden behind sub-directories.This ties in with the issue where the
tests/stdlib
use yet another "organization" scheme, see: #537.This should be done either:
tests/stdlib
organizingtests/stdlib
mirrors the currentlib
directory structureAs part of working through this issue, please note any observations useful for future projects (e.g.: many implementations of atomics).
The text was updated successfully, but these errors were encountered: