Doug Moen

@Ma-XX-oN said: "use a keyword or function call that would specify that the current file uses 1 or 3 namespaces. It can be defaulted to 1 but can be set...

@Ma-XX-oN, I'm not sure what your beef is with the proposed OpenSCAD2 backwards compatibility scheme. Existing OpenSCAD scripts that make use of 3 namespaces continue to work without any changes,...

@Ma-XX-oN "My "beef" is that you are kneecapping older scripts for not conforming to a single namespace scheme." That's a reasonable point. I would propose solving this using the `v$`,...

WebGPU is the only universal GPU API that is safe, portable, high level, high performance, and supports modern GPU features like compute shaders. Portable means: guarantees that code has the...

@bhack: The WebGPU standard only covers GPU. WebGPU corresponds to the intersection (common subset) of Vulkan, DX12 and Metal. Other kinds of accelerators (tensor processing units) are out of scope.

Your problem is actually a limitation in the STL file format. Your model isn't "2-manifold", and STL can't represent these kinds of models. AMF has the same limitation. 3MF is...

@iccor56 said "variables are not exported via use command. so any module with options has to be included instead" I think this is a bug in `use`, and should be...

@kintel: Part names are included in the CSG tree: they must be, since they change the semantics of CSG operations. Part names should appear in the *.csg output. However, marker...

@t-paul: I don't really understand your comment "Why does the actual use of the meta data need to influence the syntax". What syntax? And why do you think that my...

I don't agree that the proposed color() and part() operators have anything to do with metadata. [Maybe you could claim that the _old_ color() operator is metadata, since it has...