3 ms·
I think the Rust style that uses ”constructorless” struct initialization really makes the code too verbose in this case. It’s nice and explicit in a way but hav
by alkonaut 8y ago
I think the Rust style that uses ”constructorless” struct initialization really makes the code too verbose in this case. It’s nice and explicit in a way but having to say e.g
entrypoint: ”main”
as the argument for a shader program seems like it could be turned into a default.
Convention over configuration isn’t always the answer, but some times at least it can help reduce clutter.
In the future the api will perhaps have builders as an option.
- flohofwoe 8y agoI'm not sure if the builder pattern is better than designated initialization... AFAIK in Rust you can get something similar (fill up missing members with their default values) with ..Default::default(), like: &BlaDesc { bla: 1, blub: 2, ..Default::default() }
- masklinn 8y agoOne annoyance of this is that you can't require fields to be explicitly provided anymore. With the builder pattern, you can do so: require them in the builder constructor.