-
Notifications
You must be signed in to change notification settings - Fork 469
Clean up lazy from ASTs and back-end. #7474
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
Conversation
Now that lazy is handled user-side, there's a bunch of unused code. The type `lazy_t` is still predefined, and module `Primitive_lazy.res` still exists. Perhaps `lazy_t` can be moved user side too, and `Primitive_lazy` just moved into `Stdlib_lazy`, which seems just a wrapper for it at the moment.
rescript
@rescript/darwin-arm64
@rescript/darwin-x64
@rescript/linux-arm64
@rescript/linux-x64
@rescript/win32-x64
commit: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice cleanup! 🎉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work!
Should we also remove built in lazy_t, and move Primitive_lazy into the stdlib lazy module. |
Yes, I can do the stdlib stuff in a separate PR if you like.
Not that I know of. |
Now that lazy is handled user-side, there's a bunch of unused code.
The type
lazy_t
is still predefined, and modulePrimitive_lazy.res
still exists. Perhapslazy_t
can be moved user side too, andPrimitive_lazy
just moved intoStdlib_lazy
, which seems just a wrapper for it at the moment.