>>105896886
> swift is too slow
You can’t make a general statement like that.
I’d say it’s on par with something like ‘go’
But the language itself is very much a cleaned up C++.
As with almost all things, bottlenecks will be identified and replaced (dynamically or at build time) with assembly on some architectures.
Gcc, for example, has stdlib memcpy that is written in assembly using SIMD instructions when it detects it can do so.
Swift is using the llvm/clang optimizer, so, it’s not going to be terrible, but if you look at the from some C compilers (e.g. tcc or pcc) it will be better than that and probably faster if you use those as your C standard.
Also, it depends on how you use it. If you are writing kernel routines (for example), you won’t be using new/malloc a lot, and those things are regarded as slow due to heap maintenance, locking, and non-locality.
