alteous

What would the advantage of compiling Rust to SPIR-V be? The main problems Rust solves are memory and thread safety which as far as I'm aware are irrelevant when it...

Thanks for your PR. I would like to hold off merging for now until I have the 2.0 code ready.

The 2.0 specification is solid. I'd much prefer to see the software ecosystem building out than to see a glTF 3.0 specification.

For the sake of simplicity and ease of adoption, I hope that the scene hierarchy remains a strict tree. I say this because the [nodes and heirarchy](https://github.com/KhronosGroup/glTF/blob/master/specification/2.0/README.md#nodes-and-hierarchy) section of the...

#359 should have fixed this issue. Please re-open otherwise.

Regretfully, the only way right now is to modify the underlying JSON. https://docs.rs/gltf/latest/gltf/struct.Document.html#method.into_json

Hi, thanks for your PR. I have the exact same problem but I'm concerned replacing `HashMap` with `BTreeMap` might affect performance. Perhaps we could implement this as a feature option...

@kpreid, thanks for your input, the pointer indirection was indeed my concern. I assumed the `B` in `BTreeMap` stood for binary without looking any further into it. I stand corrected....

No major updates. The proposed solution hasn't changed, just not implemented. The type parameter as suggested previously (https://github.com/gltf-rs/gltf/issues/231#issuecomment-531463539) will not be considered.

We're proposing a boundary representation extension for solid models in https://github.com/KhronosGroup/glTF/pull/2343, notably for engineering applications. The approach taken is to provide topology information as supplementary data. This provides the best...