What parts do you think are portable to .NET Core and which parts aren't?

[mamift]

The code in this repo is very impressive. Do you have an idea as to how much of it is portable to .NET Core and how much isn't? I know the virtual memory manager is probably the part that is most likely to remain Windows-only.
I'm very interested in this as a possible all-C# replacement for sqlite. While sqlite is very good, if I want to customise things with the actual sqlite database engine I have to write C code which is something I'm not very good at and do not have time to learn.

[dementeddevil]

Thanks man - this is my pet project and something of a labour of love. You're correct - the Virtual Memory assembly is definitely Windows only. It must be possible to find equivalent *nix based APIs that could be used instead however to run on .NET Core would undoubtedly mean substituting the logic for something slower (and thus supported)

At some point I will see how much effort is involved in porting to .NET 5 depending on the feature surface. It would be a good opportunity to split the Windows bits out and provide a generic Virtual Memory implementation for other targets.

Alas the project is a long, long way from being able to replace sqlite! Let's just say "Databases are hard!"