netstandard2.0 and 2.1 targeting about bepuphysics2 HOT 3 CLOSED

A big chunk is the intrinsics, yes. There remain fallbacks for those, so tossing compilation symbols in the appropriate places would work. Unfortunately, there's a good bit of other stuff, like initialization avoidance that infects a lot of functions (Unsafe.SkipInit), plus runtime-dependent language features going forward.

from bepuphysics2.

Sorry, but this is a maintenance burden that I can't justify spending time on. It would be possible to do (and I believe Frooxius has been trying to maintain NS2.0 compatibility over at https://github.com/Neos-Metaverse/bepuphysics2, at least for part of 2.4 so far), but there's enough finnicky stuff all over the place that it would cost me quite a bit to support in an official capacity.

from bepuphysics2.

I take it it's related to Runtime.Intrinsics support.

It could be possible to provide non intrinsics counterparts for netstandard, but given you're pretty much alone in the project, I fully agree with you about the maintenance burden.

So closing the issue, thanks for the reply!

from bepuphysics2.