Increasing the limits? - classvars, Function args and ServerOptions

Development
1

Since I understand that there are API changes coming for SC 3.15.0, I wondered if now might be a good time to look at increasing some of the fixed limits within SC.
(Sorry if these have already been discussed somewhere - I am not a developer.)

Classvars
When updating TX Modular (which is a large project with many classes), I found that I had used too many classvars and had to refactor all my classes by using dictionaries to hold multiple class variables within one object (thanks HJH for suggestion). This worked but took a fair bit of time.
I wondered if this limit was fixed or if it could be increased?

Function and Synthdef args/vars/classes
There seems to be a 256 limit to the number of args and vars within a Function. This is also true for the number of classes used.
You can reduce the number of vars by using 1 dictionary to hold many vars. But still sometimes more than 256 args are needed.
This makes it hard to make large synthdefs with lots of controls. I have sometimes had to use multiple Synthdefs to do what I want.
Could this limit be increased (e.g to 256 x 16)?

ServerOptions
I wonder if the defaults should be increased, specifically for:

  • numWireBufs - I quite often bump into the 64 default limit.
  • memSize - 8192 seems low for current hardware.

Are there any other (visible/hidden) limits in SC which could also be considered?

Best,
Paul

2

Thanks for the suggestions:

re serveroptions, we’ve increased this to uncontroversial values last summer:

    var <>memSize = 256000;
	var <>numWireBufs = 512;

though in my own startup.scd I go crazy and have memsize = 2.pow(20) (1Go), numWireBufs = 8192. No idea though if that’s sensible or not :).

The other things sound like something @jordan could look into or maybe already has.