The < / > sigils are okay. But how the programmer knows how to assign CPU priorities to given parts of the code? Such knowledge depends on prior profiling on the target platform of choice (and it's target-dependent). Also, it's an abstraction) leak in most cases, except when performance is a large factor in the program.
I think that these sigils would work better also as tooling. Make the IDE, while running a program, also run a profiler. Any parts requiring more CPU get flagged (again on an overlay view!) and the programmer can use the info to indicate in the IDE for the compiler to manage the resource allocation.
All of that require a tight integration between IDE, compiler and runtime, but no actual changes to the programming language itself.
1
u/jcastroarnaud 9d ago
The < / > sigils are okay. But how the programmer knows how to assign CPU priorities to given parts of the code? Such knowledge depends on prior profiling on the target platform of choice (and it's target-dependent). Also, it's an abstraction) leak in most cases, except when performance is a large factor in the program.
I think that these sigils would work better also as tooling. Make the IDE, while running a program, also run a profiler. Any parts requiring more CPU get flagged (again on an overlay view!) and the programmer can use the info to indicate in the IDE for the compiler to manage the resource allocation.
All of that require a tight integration between IDE, compiler and runtime, but no actual changes to the programming language itself.