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…
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.
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…
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…
And don't forget Java's type erasure. Still wondering how they could actually call that a FEATURE.
That is exactly the reason I stopped reading halfway through. I couldn't take any more of his narcissism.
Ah that brings back memories. Around the same time Midori was announced we started working on the MOSA Project[1], with the similar goal to create an operating system and accompanying toolchain, completely written in…
According to that logic we can also go ahead and ban all products that rely on the chemical element Bromine.
Because hello_world returns an IronResult, which in turn is just a simple Result type from Rust. Note that the status::Ok is different from the Ok(...). Iron::new expects a function that returns a Result type, so it has…
What you want to get down to is the intrinsic dimensionality. Go below that and you start discarding useful information.
That depends on your clustering algorithms. If it is for example based on shared-neighbor information, then you end up with the same clusters as you did before scaling. And in your example, I get: (A, B) < (B, C) < (A,…
How do traits limit you? Could you give an example?
Can't agree more. XMonad is what I based my Rust window manager on. Nice, clean, easy to understand code base. No other window manager gave me so many insights into how a WM works.
And as soon as everyone starts using s/he, bigender people get annoyed that heshe wasn't used. It's language...it's difficult to get everyday usage "normalized" into a different direction.
And done
Thanks, I will look into it. But tomorrow at the earliest. Today I'm out to celebrate the last ever exam I just passed.
Except for 2 exceptions, only for interfacing with xlib, as the calls to rust-xlib involve raw pointers (because rust-xlib is just a plain c-binding wrapper around xlib). The 2 exceptions are: loading of the config…
Xephyr is just for testing. You can run wtftw completely standalone when you use it in your .xinitrc for example. It's still a bit buggy though. Works perfectly fine here. Been using it as my default WM for 2 weeks…
As soon as I figure out how to do that. But I need only minimal functionality, so I don't expect it to be _too_ difficult. I figured I should start with the Weston shell and figure it out from there.
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…
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.
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…
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…
And don't forget Java's type erasure. Still wondering how they could actually call that a FEATURE.
That is exactly the reason I stopped reading halfway through. I couldn't take any more of his narcissism.
Ah that brings back memories. Around the same time Midori was announced we started working on the MOSA Project[1], with the similar goal to create an operating system and accompanying toolchain, completely written in…
According to that logic we can also go ahead and ban all products that rely on the chemical element Bromine.
Because hello_world returns an IronResult, which in turn is just a simple Result type from Rust. Note that the status::Ok is different from the Ok(...). Iron::new expects a function that returns a Result type, so it has…
What you want to get down to is the intrinsic dimensionality. Go below that and you start discarding useful information.
That depends on your clustering algorithms. If it is for example based on shared-neighbor information, then you end up with the same clusters as you did before scaling. And in your example, I get: (A, B) < (B, C) < (A,…
How do traits limit you? Could you give an example?
Can't agree more. XMonad is what I based my Rust window manager on. Nice, clean, easy to understand code base. No other window manager gave me so many insights into how a WM works.
And as soon as everyone starts using s/he, bigender people get annoyed that heshe wasn't used. It's language...it's difficult to get everyday usage "normalized" into a different direction.
And done
Thanks, I will look into it. But tomorrow at the earliest. Today I'm out to celebrate the last ever exam I just passed.
Except for 2 exceptions, only for interfacing with xlib, as the calls to rust-xlib involve raw pointers (because rust-xlib is just a plain c-binding wrapper around xlib). The 2 exceptions are: loading of the config…
Xephyr is just for testing. You can run wtftw completely standalone when you use it in your .xinitrc for example. It's still a bit buggy though. Works perfectly fine here. Been using it as my default WM for 2 weeks…
As soon as I figure out how to do that. But I need only minimal functionality, so I don't expect it to be _too_ difficult. I figured I should start with the Weston shell and figure it out from there.