tm-ms

Valid topic, but not worked on in the foreseeable future.

This would actually be very quick to be changed. The method `StorageEntityInitializer#fillBuffer` would simply have to be replaced by a call to a StorageFileReader which could be passed in `StorageFileManager#initializeForExistingFiles...

I have implemented the two methods BinaryValueTranslators#removeLazyReference BinaryValueTranslators#wrapWithLazyReference However, this topic is not trivial: - The mapping can't be done automatically/implicitely. - The removing translator even can't work at all...

A simple solution could be, to "somehow" mark Lazy References to be eager. An eagerly loaded lazy reference could easily be removed and replaced by its actual reference. However, then...

If there is an equivalent to Unsafe in Graal, then we can write a suitable MemoryAccessor for it. The failed test uses JDK (Oracle JVM) specific code, see stacktrace. Maybe...

> https://medium.com/graalvm/instant-netty-startup-using-graalvm-native-image-generation-ed6f14ff7692 > here are some information how native images are built I don't know if this information is meant as a reply to my comment. If it is, I...

> > If it does not work on Graal, then the question is: How does it have to be changed to access sun.misc.Unsafe on Graal? > > Or, if sun.misc.Unsafe...

Currently, without recognizing and forbidding such a use, it can cause the the problem described in microstream-one/microstream-public#10. However, and appropriate fix for microstream-one/microstream-public#10 will prevent that. But there can still...

Some thinking brought the conclusion that such invalid cases cannot be recognized, because they moreless "do not exist". It is perfectly valid that some constant field (and the instance identified...