My experience is very limited here, but I have used TockOS on one of their dev boards. That was very pleasant, no stdlib makes it a little harder than std Rust, but still felt more deterministic than writing in C.
My experience is very limited here, but I have used TockOS on one of their dev boards. That was very pleasant, no stdlib makes it a little harder than std Rust, but still felt more deterministic than writing in C.
It's probably even more important for professional embedded engineers, where the hardware decisions may not even be made by the software developers, for various reasons.
Advantage over what? This can be said about the majority of programming languages
For example, I’ve recently done an embedded ARM Linux project where I used C# and .NET Core for higher level parts, C++ for lower level, [DllImport] and C API between the two.
Ease of use is the same when I consuming the C API from e.g. C++. No disadvantage for C#.
C# doesn't support this out of the box, but it can be easily done by post-processing the generated assembly. There's a NuGet package for that.
https://www.nuget.org/packages/UnmanagedExports
I'm not sure if any of that works on other platforms, or with .NET Core. Probably not.
Didn’t work because that recompilation step broke debugger, and invalidated .PDB debug symbols.
I also have some experience with Java, JavaScript and PHP. They don’t.
Python: https://stackoverflow.com/a/33485103/126995
Basic: http://codingdomain.com/visualbasic/win32api/callback/
About the performance… Neither of these languages are particularly fast in the first place :-) But I don't see a reason why these callbacks might be too slow.
So, I wouldn't necessarily say that's a blocker. Obviously everyone should make the best choice given their business requirements, etc.