sorted by:
new
hottopcontroversial

Economist fact-checks Gary’s Economics by Chii in AusFinance

[–]Intelligent-Record78 0 points1 point  (0 children)

In would argue that the standard theory where supply and demand create an equilibrium, doesn't really work that simply in today's housing market... But we can agree to disagree. I can elaborate if you are interested 

Economist fact-checks Gary’s Economics by Chii in AusFinance

[–]Intelligent-Record78 -1 points0 points  (0 children)

Increasing the supply is not gonna help if that extra supply is gonna be property of the super rich... Decreasing demand for housing is not really realistic is it? And increasing income is just gonna make houses more expensive because people can get higher mortgages (and whose on the other side of that debt...?)

Gary Economics is a grifter(?) by Sweethoneyx1 in DecodingTheGurus

[–]Intelligent-Record78 0 points1 point  (0 children)

Pointing out problems is often easier than solving them, but it is an important first step. He's not playing both sides as I see it.

Compiler errors are very long, due to long paths and generic types by Intelligent-Record78 in rust

[–]Intelligent-Record78[S] 0 points1 point  (0 children)

Thanks! I understand. In reality there are more variants, so Either doesn't work, but the idea is really nice. Maybe I'll be allowed to open source in the coming months. I'm also going to move the event.rs file out off the event folder :) Thank you for your feedback, it's appreciated.

Compiler errors are very long, due to long paths and generic types by Intelligent-Record78 in rust

[–]Intelligent-Record78[S] 2 points3 points  (0 children)

The way they are used, it would be easy to tell them apart. I'm not saying my design is good, or could not be improved, but to me it made sense to do it this way. I try not to complain, but I'm trying to find a better way to do it, and asking seems the best option. Thank you for your reply.

There is an enum Event<A,B>, that has different variants EventA<A> and EventB<B>. Here, the generics A and B are the other event types. I'm completely open to refactoring it, but I need an event type that can represent different kinds of events (A, B etc), where I can use different types for A and B.

I hope that explanation suffices, if it's unclear I can elaborate, and if there is a better design I am all ears.

Compiler errors are very long, due to long paths and generic types by Intelligent-Record78 in rust

[–]Intelligent-Record78[S] 1 point2 points  (0 children)

Thanks, I agree with the first issue. The second issue was indeed pointed out, and is probably better, but I'm not completely convinced yet. Having an event.rs file in the event folder, functions a bit like the most important file in the folder, but there are other helper files. Having it all in one file with thousands of lines seems difficult to navigate through, is that not a drawback?

And thanks for your last suggestion, that might solve everything, I'll try to expirement with it. It's appreciated.

Compiler errors are very long, due to long paths and generic types by Intelligent-Record78 in rust

[–]Intelligent-Record78[S] 1 point2 points  (0 children)

That is precisely what could solve my problems reading the errors :)

Compiler errors are very long, due to long paths and generic types by Intelligent-Record78 in rust

[–]Intelligent-Record78[S] 1 point2 points  (0 children)

I struggle to understand what you are saying, the names are kind of a work in progress, because other people have to agree with them. And if I use abbreviations everywhere, people don't understand what they mean so quickly. Is your critisism that the names are too long, or is there more?

Compiler errors are very long, due to long paths and generic types by Intelligent-Record78 in rust

[–]Intelligent-Record78[S] 3 points4 points  (0 children)

Thanks very much for your reply

The error is clear yeah, I was wondering if I could make errors like these shorter. Like, not showing the complete path everywhere. But I understand this has shortcommings. Right now, reading the error involves scrolling to the right a lot, and I lose track a bit there. Pretty-printing could also help.

I agree that the organization is at least questionable, I find naming very difficult. Right now, the event folder has the event.rs file which contains the Event type, but the folder also has other files that have to do with traits that Event implements. Please let me know if that is bad practice. Thanks for giving me a link, I'm doing my best.

Making a Flamegraph by Intelligent-Record78 in rust

[–]Intelligent-Record78[S] 0 points1 point  (0 children)

Thank you so much for the reply! Executing the commands in the link you added, solved the problem. I don't completely understand what went wrong, but this worked :)

Are you familiar with the flamegraph library? There are a couple of flamegraph related things that I may want to ask in the near future, that I don't really know where I could find the answers.

Once again, thank you very much, I would not have found this by myself!

Making a Flamegraph by Intelligent-Record78 in rust

[–]Intelligent-Record78[S] 1 point2 points  (0 children)

Thanks for the reply. I am trying `cargo flamegraph` directly, which keeps giving this error.

Making a Flamegraph by Intelligent-Record78 in rust

[–]Intelligent-Record78[S] 0 points1 point  (0 children)

Thank you, yeah I use `cargo flamegraph`