Please show us real code where std::unique_ptr vs std::shared_ptr makes a considerable difference (with benchmarks). A pointer indirection causes a cache miss? A shared_ptr can be optimized to unique_ptr if it's not…
I do not expect anyone to code a C or C++ library with no awareness of memory errors. This isn't a safe language on top of C++. If you target C++, you need to know it. On the other hand, if you only know "safe"…
Let's discuss it in https://github.com/pfusik/cito/issues/30
I'd like to rewrite cito to Ć at some point. One problem is that it's written in a fairly recent C#, so either Ć would need to catch up with two decades of C# development or the codebase be downgraded to an older…
Yes, benchmarking is interesting. I will post benchmarks of different target languages.
> Are there any samples of the final sources? https://github.com/pfusik/cito/issues/21 I generally check-in just the Ć source and not the translations, but if you want a quick look at the generated C code, here's some:…
Yes, you can make a memory leak when targetting C, C++ and Swift. Same as when you code in C, C++ and Swift directly.
There are still many Windows programs that default to current Code Page instead of UTF-8. I prefer to have the encoding explicit in the file contents rather than rely on some external file type configuration. This is…
Please show us real code where std::unique_ptr vs std::shared_ptr makes a considerable difference (with benchmarks). A pointer indirection causes a cache miss? A shared_ptr can be optimized to unique_ptr if it's not…
I do not expect anyone to code a C or C++ library with no awareness of memory errors. This isn't a safe language on top of C++. If you target C++, you need to know it. On the other hand, if you only know "safe"…
Let's discuss it in https://github.com/pfusik/cito/issues/30
I'd like to rewrite cito to Ć at some point. One problem is that it's written in a fairly recent C#, so either Ć would need to catch up with two decades of C# development or the codebase be downgraded to an older…
Yes, benchmarking is interesting. I will post benchmarks of different target languages.
> Are there any samples of the final sources? https://github.com/pfusik/cito/issues/21 I generally check-in just the Ć source and not the translations, but if you want a quick look at the generated C code, here's some:…
Yes, you can make a memory leak when targetting C, C++ and Swift. Same as when you code in C, C++ and Swift directly.
There are still many Windows programs that default to current Code Page instead of UTF-8. I prefer to have the encoding explicit in the file contents rather than rely on some external file type configuration. This is…