Jordan Brown

Yes to all of that. "Some of your documents ..." has the same problem of being awkward when there's only one document. My preference would be to handle the one-tab...

I built this fork for a project where I wanted to import a 2.5D drawing from Inkscape, and it worked perfectly. Note that you can set the ID of individual...

@t-paul 's point about calculated keys is valuable. A related topic would be where even the number of keys is dynamic. Probably one of the forms should be ``` object([[name,...

This made me think about whether the inverse operation - turning an object into a list of name-value pairs - was necessary. I don't think so. You can already (in...

Getting more general, I don't think it would need to be limited to a single such argument. There are probably some devilish details, but it seems sensible to allow one...

I think we do want a `{ ... }` object construction syntax. It's just nicer for building static objects. But also I think it plays well into the #3956 data=render()...

Having done only "architectural" review - that is, what does this function look like to the OpenSCAD program, and not any code review - I'm OK with letting it in...

Well, we'll see what others say, but I think it's OK. I want objects to be a first-class citizen, which suggests dedicated syntax, and I like the idea of combining...

Should probably be experimental. Look at examples for ExperimentalImportFunction, one line each in src/core/builtin_functions.cc, src/Feature.cc, src/Feature.h.

concat is not yet valid for objects. For removing entries, I was debating whether `name=undef` should set the value to undef, or should remove it. Although undef is a theoretically...