mojopkg files. They are in the docs but there are 0 valid use cases for them on the user side. To this day I still don’t understand why it’s still in the docs and why it’s not treated as an implementation detail. Either it should be in the docs and clearly state in which case they must be used, either they should be removed from the docs. There are been a few discussions with the compiler team about it, and every time the answer was “It’s an implementation detail but we expose it just in case it’s useful”
Some background: Version compatibility for .mojopkg files - #3 by denis