| 11 Aug 2020 |
 cwfitzgerald | I don't think all the types are being replaced though | 04:58:59 |
| cwfitzgerald | Things like the features bitflags and other things of that nature are still common between them | 04:59:25 |
 kvark | hmm, right. A handful of types will persist | 05:03:15 |
 kimundi | So should I avoid redefining types that do not use Cow? :) | 06:13:06 |
| kimundi | Actually, how should I handle Descriptors with Default impls and/or builder impls | 07:29:02 |
| kvark | kimundi: let's redefine all descriptors, to be consistent | 12:00:49 |
| kvark | builder impls will go away, default impls... not that important after your cowhidation work | 12:01:12 |
| kimundi | ALright, I'll try to do that | 12:02:42 |
| kimundi | kvark: So should I basically copy everything that is currently re-exported from wgpu_types? | 12:47:30 |
| kvark | not everything, just the descriptors | 12:48:10 |
| kimundi | kvark: Alright, I think I've now replaced every type that contained a Cow, and the example don't use Cow or Borrowed anywhere anymore | 13:29:05 |
| kimundi | I might have missed some re-export from core though | 13:29:18 |
| kimundi | And the ShaderModule enum still contains a Cow, but I think thats intentional | 13:29:31 |
| kimundi | Notable, I did not need to replace all Descriptors for this | 13:30:00 |
| kvark | thank you! | 13:42:01 |
| kvark | On an unrelated note, I was thinking: is there a single implementation of the VUs (valid usage rules) in Vulkan spec? Given how often the validation layers miss stuff, it seems mind-blowing that applications have to follow the spec, which isn't implemented really by either the drivers (they don't care about checking VUs, they just assume they are fulfilled) or the layers. | 13:43:32 |
 Kangz | The VVL (Vulkan Validation Layers) are supposed to implement the VUs and they only recently gained alpha support for pipeline barrier stuff. | 16:15:55 |
| Kangz | But given the number of issues WebGPU finds in Vulkan, I'm sure there's a lot of fixes to the spec that will be needed. | 16:16:20 |
 m4b | its almost as if specs written by humans have formal ambiguities ; ) | 23:08:20 |
| m4b | thankfully we all learned our lessons from the iso C and C++ "specs", and got better at using formal languages for these kind of things | 23:09:01 |
| * m4b stares wistfully at The Definition of Standard ML | 23:10:30 |
| m4b | you don't have to respond to my trolling kvark :P | 23:13:20 |
| kvark | I'm not complaining about ambiguity. I'm complaining about the lack of spec implementation. IMO a spec that's not implemented is not a real spec | 23:13:34 |
| m4b | wouldn't, e.g., an intel vulkan driver by an implementation of the vulkan spec? or do you mean something else? | 23:14:46 |
| kvark | It doesn't implement VUs | 23:15:21 |
| m4b | or you want some kind of assurances that the implementation meets the specification? (a generally very difficult problem in formal methodologies) | 23:15:22 |
| kvark | VVL are supposed to implement VUs but they are still(!) WIP | 23:16:02 |
| 12 Aug 2020 |
| kvark | cwfitzgerald: I'm not going to merge https://github.com/gfx-rs/wgpu-rs/pull/501 until you finish your mindful review :) | 03:24:42 |
 hecrj | Lachlan Sneff: What do you mean by "conflict with bevy"?
Also interested to know why do you think an ECS approach is more fitting for GUI. My experience is that dealing with hierarchical, mutable data structures in an ECS is quite painful. For instance, in order to change the text of the button example in Bevy, you need to give up some type safety: https://github.com/bevyengine/bevy/blob/d488d4e308dd1304347d22ad8728d08eb6abf568/examples/ui/button.rs#L41
| 12:33:05 |
| hecrj | * Lachlan Sneff: What do you mean by "conflict with bevy"?
Also interested to know why do you think an ECS approach is more fitting for GUI. My experience is that dealing with hierarchical, mutable data structures in an ECS is quite painful. For instance, in order to change the text of the button example in Bevy, you need to give up some type safety: https://github.com/bevyengine/bevy/blob/d488d4e308dd1304347d22ad8728d08eb6abf568/examples/ui/button.rs#L41
| 12:33:38 |
