We are forcing RTTI for all classes used in casts, some light code changes are required for this that our compiler will hint at.

[One of the authors here]

Type++ analyzes all application code and infers which classes are ever cast. All of those classes are adapted to include type information (in the form of an RTTI field). All casts are then changed into explicit casts.

As a dialect, some light changes are necessary and we evaluate the amount of code changes --- which are usually small. This gives us type safety for even large programs as evaluated.

A short blog is available here: https://nebelwelt.net/blog/2025/0226-typepp.html

Excellent! Do you have any plans to get this feature added into clang or something? How could I use it? If it's in the paper you can just say so. I haven't had time to look at it carefully.

Our prototype is at https://github.com/HexHive/typepp/ so you can run it in your testing environment

TBH, I don't expect much more from large corporations. From an economical standpoint, the cost of fixing the bug is higher than the lost revenue if I move my business somewhere else. The engineer and open source enthusiast in me still wants to report the bug so that they can fix it. I wish I'd learn ;)

https://en.wikipedia.org/wiki/Die_Gedanken_sind_frei Unfortunately not.