Hmm. I was hoping that the documentation discussion would talk about modernization or better tooling but that doesn't seem to be the case.

@anhnha I'd suggest never even bothering with Subscript in functions or programs or any of that. It's fundamentally display object and I think should be treated as such. Indexed has some special usages when working with enumerated variables and stuff but I'd still avoid it in almost all cases.

When you're makin' a Row, ya gotta Riffle in a Spacer!

@b3m2a1 I have spent some time looking at how the kernel code is implemented, and still I end up making it up as I go. For user-facing functions I do use System-Private-Arguments to quit early and issue a message about the wrong number of arguments or wrong options.

Then I try to use an internal function, MainFunction calls iMainFunction but only returns its value if it isn't $Failed, and have a Condition so that if iMainFunction returns $Failed then MainFunction returns unevaluated

but you know all of that, maybe it isn't what you are asking

I try to stay away from mutable objects, instead making functions that return a changed object

so there is no method that changes the molecule, but instead returns a new molecule with the changes

Yeah I was hoping there’d be a single function that’d help do all the boilerplate

Usually I also avoid mutability but it’s the most consistent and logical way to do what I’m trying to do

@Feeds Wow @CarlLange didn't realize you were the reason this was streamed

@b3m2a1 ??

@b3m2a1 I was? I didn't know that either - and I missed that one and all!