Mike McCrea

> CmdPeriod.run; // consume all of the RT memory AND some more beyond, but now it fails ?! This problem may or may not not be central to the issue...

@capital-G >edit: also got [/rtmem.reply, 8369024, 8368832] after a "cold boot" did you discover what was going on with this issue?

Interesting feature! I'm not starting a full review, just some quick comments after a glance at the updated documentation.

I agree this is a good addition. There's a meta discussion that could be had about proper/encouraged construction and setting of members, but that's on the class authoring side. The...

We'd also want to check the alignment with behavior of `T2K`. https://github.com/timblechmann/supercollider/blob/91dfacf5f2f1bf5dd5a0447e581fd1b871549abc/server/plugins/LFUGens.cpp#L1297-L1307

>But, one such concrete advantage has been proposed -- if a kr UGen receives a faster-than-kr input, then it becomes possible to trigger faster than half-kr (which is currently not...

> Note though that this last case is handled by T2K: My example was done assuming we're advocating for one of the advantages listed above: >Control-rate UGens would be able...

Thanks all for getting this rolling! >All arguments should be documented (as specified in this document). If language would be duplicated in various places in one document, it is ok...

A question has surfaced recently also about capitalization, in particular for argument descriptions. I tend to favor [sentence case](https://developers.google.com/style/capitalization), even if the description isn't a complete sentence. This also applies...

Reopening for the moment... I'm not sure where follow-on discussion is meant to take place (I can move this elsewhere if needed)... > I've noticed the strong:: (not code::) tags...