Future RFCs

This wiki page lists RFCs that are in preliminary stages -- either being actively worked on, or RFCs that just exist as ideas right now.

In progress

• sclang debugger (Brian, Scott C)

Ideas

• macOS volume safety (Nathan).
• Improvements to sclang debugging. See https://github.com/supercollider/supercollider/issues/281, https://github.com/supercollider/supercollider/issues/307, https://github.com/supercollider/supercollider/issues/308.
• Server-side UGen metadata system. (see https://github.com/supercollider/supercollider/issues/2300)
• Machine-readable post output from sclang (what does this mean? - Brian)
• A new NRT mode with an OSC socket. (see https://github.com/supercollider/supercollider/issues/279)
• Merging or incorporating Bela work (IMO doesn't need an RFC - Brian)
• Including scnvim in main distro (Brian)
• Unicode-aware Strings and Chars. (see https://github.com/supercollider/supercollider/issues/288)
• Language externals (language plugins).
• Dynamic class library compilation.
• Reform of search paths used by sclang, scsynth, and scide to ease in use cases such as standalone installations and installation of multiple concurrent versions of SuperCollider.
• AbstractObject class, similar to Ruby's BasicObject. A sketch is here: https://github.com/telephon/Neutral This would allow e.g. wrappers around objects that can carry metadata, that can implement safe object prototypes, and that can forward messages in a particular way.
• Protect standard EQ ugens (LPF, HPF, etc) from unstable coefficient settings.
• Global oversampling (or undersampling!) of the server, with support for custom FIR and IIR polyphase antialiasing filters as well as a good selection of built-in options.
• Bump C++ standard to C++17
• Change master branch name to main to be less racist