-
Notifications
You must be signed in to change notification settings - Fork 355
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
add intro #1928
base: main
Are you sure you want to change the base?
add intro #1928
Conversation
|
||
## How to read this guide | ||
|
||
While this guide is not designed to be read in sequence, it is still recommended to do so. This book gives a surface level overview first with very simple examples and then explores Rust's type system magic. Astute readers may skip to more interesting chapters. |
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.
Hmm, I'm a bit nervous about focusing on the type system magic: while interesting, I don't think it's relevant to most readers.
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.
Yeah, this is mostly a placeholder as I want to delve how add_systems and registering works under the hood.
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.
To explain the architecture it is quite surprising that there are no real macros involved. This follows from the IntoSystemConfig impls which the type checker automatically deduces. Other frameworks, like actix, usually annotate the "system" functions with macros. It's not the case with Bevy, which is quite surprising, and elegant.
Co-authored-by: Alice Cecile <[email protected]>
Add a very simple introduction