codingbinary

Same here. I thought that's pretty normal. The generic one looks pretty...normal to me. The clang version iss too much compiler voodoo and kinda makes it less readable.

Back when MOSA got created, we were aiming for a pure approach. For example, we were trying to use as few intrinsics as possible and a mostly architecture agnostic approach.

Furthermore we also focussed on Mono compatibility (that was way before CoreCLR came out).

Source: Ex co-creator of MOSA

I'm just wondering how the same statement (if the data would show it) would be perceived if it would be said for males.

Studies could also show that there is a higher chance for mothers to quit along half the way due to child-related reasons (made up studies for the sake of argument). That on the other hand would be considered misogny. And I'd take it with a grain of salt as the sample sizes are vastly different.

That being said, do you have a link somewhere? Would really be interested to read that.

Plus, wouldn't that contradict the whole idea of "we are all equal. Men are not better than women" but suddenly stating the opposite is totally fine?

The data on this would really be interesting.

Which is true, because your child should be your #1 priority. Regardless of your gender.

Wow, they didn't have SSA in there yet? That's quite a surprise as, as far as I understand, SSA is pretty common nowadays in compiler techniques. Even for the MOSA compiler we had this.

"Homogenous european states."

Did I miss something?

Then that's the reason. The config is a dylib, so I have to force it into using jemalloc, which I cannot do when using stable.

But that wasn't always the case, right? I think around the time of 1.3/1.4 jemalloc was not the default.

Really? Last time I checked it still didn't work. Will have to try when I get home.

The problem was that the config is compiled into a dynamic library and gets passed the config struct. The old alloc method kind of died on me when the dynamic library was trying to alter that struct. So I had to enable jemalloc to keep it from crashing.

Yep, exactly that killed my window manager on stable. I _have_ to use nightlies now, because I need the alloc_jemalloc feature.

The one is on a language level, the other on an application/framework level.

Type Erasure is the reason you can't use builtin types as generic arguments. And in a lot of cases it forces you to cast.

And as type erasure happens very, very early in the compilation process, you lose a lot of static type information the compiler could act on or give you warnings.

And don't forget Java's type erasure. Still wondering how they could actually call that a FEATURE.