-
Notifications
You must be signed in to change notification settings - Fork 9
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
RFC: module re-organization #20
Conversation
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.
My only thought: any reason we want to exclude neon::thread
from the prelude? Do we consider it advanced enough to bury a little?
Otherwise this is solid!
@tptee It just felt like more of a specific use case, and not something you would be likely to want to use in most projects. But we can add it to the prelude compatibly if it becomes clear it's being used most of the time. |
📢 This RFC is going into final comment period! We will plan to merge it within a week if there aren't significant new issues that arise in the next week. 📢 |
…, more nuanced motivation.
…cation isn't exactly the goal, so much as being more intuitive.
…n::thread` back to the original `neon::task`.
A backwards-incompatible reorganization of the public API organization of
neon::*
to make it easier and more ergonomic to import Neon APIs.Rendered
Here's a temporary site where you can browse the API docs.