Torsten Paul

Uh, sorry for the delay, that somehow slipped through.

It seems to do that for a while. E.g. set config value to 1000 and ``` difference() { cube(); for (a = [0:9]) { intersection() { sphere(); cylinder(); } }...

Likely caused by the experimental feature "lazy-union". This one is unstable and not generally recommended to be enabled.

Why does the actual use of the meta data need to influence the syntax? All meta data will need to be in the CSG tree anyway. Some would be only...

Using the `part()` syntax is only possible for module instantiations, not for variable, function or modules definitions. At least I don't see how that would be possible.

Yes, I'm not talking about the behavior, e.g. how color will be handled by the CSG operations. In my view the color is a property of a specific node /...

Yes, the modifier `#` could be a short-cut, but what I mean is, it's attached to the node, which is why it's not possible to write `# { cube(); sphere();...

Well, I guess we will just not agree on what's easier to read. That's not a big deal. Back to the main question "how do I do that for module...

Yes, there's a number of topics to solve to get this feature in. The 2 main parts would be the ability to pass along color information inside the geometry engine...

This sounds like a request for a totally new program.