-
Notifications
You must be signed in to change notification settings - Fork 342
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
Migration Guide: 0.4 to 0.5 #107
Conversation
Migration guide for systemparams and insert()
} | ||
|
||
// 0.5 | ||
fn foo(r1_thru_3: (Res<Thing1>, Res<Thing2>, Res<Thing3>), r4: Res<Thing4>, ... r15: Res<Thing15>) { |
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.
fn foo(r1_thru_3: (Res<Thing1>, Res<Thing2>, Res<Thing3>), r4: Res<Thing4>, ... r15: Res<Thing15>) { | |
fn foo(r1_thru_3: (Res<Thing1>, Res<Thing2>, Res<Thing3>), r4: Res<Thing4>, ... r12: Res<Thing12>) { |
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.
oh, I was too quick to comment. I see now how its using the nested for the first three ^^
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.
Maybe it would be good to pattern match the first argument to help with noticing the change?
fn foo(r1_thru_3: (Res<Thing1>, Res<Thing2>, Res<Thing3>), r4: Res<Thing4>, ... r15: Res<Thing15>) { | |
fn foo((r1, r2, r3): (Res<Thing1>, Res<Thing2>, Res<Thing3>), r4: Res<Thing4>, ... r15: Res<Thing15>) { |
How could I contribute to this? Am I supposed to make PRs against the branch of carts fork? |
Add points 4&5 about Events API and add_resource => insert_resource
Documentation Improvements
Address migration point 30
Section 7: Timer and Stopwatch
This adds the initial migration guide page. This is intended to be a collaborative effort. To contribute, leave a comment on 0.4 to 0.5 migration guide issue claiming one or more unclaimed items, then create a pull request to this branch.
Each migration item should have a description of the change (with rationale if you anticipate a negative response), descriptions of breakage symptoms (when that is relevant and non-obvious), and small before/after code snippets where relevant.
Todos: