Scrutor VS valhalla-docs

You can with MS's default DI as well via scrutor.

if you are heavily invested in autofac you can replace the build in DI with another container. at this point i don't think it is that necessary. especially if you use scrutor. it gives your some nice assembly scanning registration that autofac/simple injector give https://github.com/khellang/Scrutor

If you wouldn't mind, I have one additional question. If I wouldn't bother to remove this loading, how could one add that as service when using DI? I have found tool called Scrutor (https://github.com/khellang/Scrutor), is it something commonly used in situation like this?

I much prefer using Scrutor and asbly scanning myself. https://github.com/khellang/Scrutor

you can also use Scrutor to get closer to Autofac functionality https://github.com/khellang/Scrutor

That can't be the only justification, because you can easily register services using reflection without using MediatR.

I might suggest additional registration time extensions to modify the behavior as needed on classes. Take a look at Scrutor for some inspiration on API specifically.

There is a package that simplifies it for you if you want. But not everybody agrees that automatic registration is good pattern, so you have a choice.

What isn't clear for me from https://github.com/openjdk/valhalla-docs/blob/main/site/design-notes/state-of-valhalla/02-object-model.md is whether or not value types will indeed be headerless.

Regarding type erasure, see https://github.com/openjdk/valhalla-docs/blob/main/site/design-notes/in-defense-of-erasure.md for a justification. Note in particular that not doing erasure would have forced languages like Scala to follow Java's semantics. In cases where erasure is actually a problem, you can work around it with classes like https://fasterxml.github.io/jackson-core/javadoc/2.2.0/com/fasterxml/jackson/core/type/TypeReference.html.

Here's a (relatively recent) post on type erasure from the lead of the value types project at Oracle https://github.com/openjdk/valhalla-docs/blob/main/site/design-notes/in-defense-of-erasure.md

If you want to read something a little more formal and fleshed out, try scanning through this document, and then come back again and tell me that Brian doesn't understand your suggestion.

Source

I haven't been following it incredibly closely, but I have checked in from time to time. It's a hard problem, but there's a lot of real progress (https://github.com/openjdk/valhalla-docs/blob/main/site/desi...).

I'd wager that it will ship by the next LTS, in 2024.

Quotes from here