Optimize how code strings are built up to reduce the library size

As part of the nanoColor project, we have been trying to reduce the size of the library. Currently nanoColor is between 1.5-3 MB, depending on the platform and compiler flags but the goal is to get it down to 1 MB or less.

As we have profiled where the size of the existing library comes from, we noticed that there is a lot of size coming from modules that create code. For example, all the modules that build shader code for various GPU languages are among the largest. Another example is the way Exception message strings are built. All of this uses a pattern which is nice to read in the code but which creates a lot of temporary string objects that bloats the library size.

This proposal is to find a better way to build up these long strings from components that is both easy to read in the code but which is much more efficient in terms of the size of the library.

Commencez par profiler les modules qui construisent du code de shader pour les langages GPU ainsi que la construction des chaînes de caractères des messages d’exception décrite dans l’issue. Comparez les approches pour assembler de longues chaînes, puis vérifiez que la taille de la bibliothèque est réduite jusqu’à l’objectif indiqué de 1 Mo ou moins sans perdre en lisibilité.

Rédigé par le modèle d'indexation à partir du texte de l'issue.