-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Add node input type support for f32 to enable usage on GPU
#3095
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
Changes from 7 commits
7922e11
c44beb2
6f5e97b
61f2066
3c4fc9d
d6319f6
6917695
68c0e00
bff4feb
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -805,9 +805,11 @@ mod test { | |
| construction_network.generate_stable_node_ids(); | ||
| assert_eq!(construction_network.nodes[0].1.identifier.name.as_ref(), "value"); | ||
| let ids: Vec<_> = construction_network.nodes.iter().map(|(id, _)| *id).collect(); | ||
|
|
||
| // If this assert fails: These NodeIds seem to be changing when you modify TaggedValue, just update them. | ||
| assert_eq!( | ||
| ids, | ||
| vec![NodeId(13743208144182721472), NodeId(4607569396187877965), NodeId(16950305885390329527), NodeId(15151181027373658932)] | ||
| vec![NodeId(2791689253855410677), NodeId(11246167042277902310), NodeId(1014827049498980779), NodeId(4864562752646903491)] | ||
|
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is this comment I left correct? Based on git history, I see them being updated frequently
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, I think the test network contains a
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @0HyperCube what about the comment right above, which github is hiding?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It seems fair. I don't really see why it matters if the node ids aren't stable across different commits. However most modifications to the TaggedValue take place under the U32 so it probably shouldn't break too much. |
||
| ); | ||
| } | ||
|
|
||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.
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.
Let's please call this
FVec2because the user-facing name forDVec2is already "Vec2" and we need to avoid the confusion of the internal version being given the opposite name of the user-facing version. And probably the same forAffine2->FAffine2for consistency. This also lets us discriminate between them in the future for rename purposes if we figure out how to clean this up once there is more Graphene infrastructure in place to handle numeric precision and units.