The rise of wgpu

Re:The rise of wgpu by alkonaut on Thursday March 07, 2019 @12:49PM (#19330229)

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.

[ Parent | on HN ]

Re:The rise of wgpu by flohofwoe on Thursday March 07, 2019 @01:02PM (#19330371)

I'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()
    }

[ Parent | on HN ]

Re:The rise of wgpu by masklinn on Thursday March 07, 2019 @01:31PM (#19330684)

One 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.

[ Parent | on HN ]