<y​pavtv97lx:matrix.org> Wouldn't fixed inflation, for example: 1% which would result in higher reward for block with time be better than what we have now ? it would create even bigger incentive to mine and we wouldn't have to worry about price not following energy cost etc. ?

Possibly. IIRC this is what Aeon did.

It's really a case of "try it and see how it works 100 years down the line".

<y​pavtv97lx:matrix.org> was not aware of the Aeon doing it, will check it.

<y​pavtv97lx:matrix.org> it's an economical dilemma, from programming point of view it's an easy task if I'm correct ?

Yes.

<e​ndor00:matrix.org> > and we wouldn't have to worry about price not following energy cost etc. ?

<e​ndor00:matrix.org> But we would have to worry about exponentially depreciating coins, due to the inflation. It's a self-balancing system. PoW will *always* have to worry about the cost of energy, because that's exactly one of the things that keeps the system in balance.

<e​ndor00:matrix.org> (/offtopic)

<0​xfffc:matrix.org> Any idea how to clean up this variable here: github.com/monero-project/monero/bl…ba7b1/src/common/dns_utils.cpp#L330 We basically create a class `scoped_ptr` and just use that in that variable. two points to keep in mind: 1) none of the smart pointer libraries have something like `&` that we use there. 2. After getting rid of scoped_pt<clipped message>

<0​xfffc:matrix.org> r, gcc's __attribute__((cleanup(freefunc))) would be perfect use there. But MSVC support is blocking us from using that.

<0​xfffc:matrix.org> Any idea how to clean up this variable here: github.com/monero-project/monero/bl…616140bb7267b16ba7b1/src/common/dns\_utils.cpp#L330 We basically create a class `scoped_ptr` and just use that in that variable. two points to keep in mind: 1) none of the smart pointer libraries have something like `&` that we use there. 2. After getting rid of scoped\_<clipped message>

<0​xfffc:matrix.org> ptr, gcc's _ _attribute_ _((cleanup(freefunc))) would be perfect use there. But MSVC support is blocking us from using that.

<0​xfffc:matrix.org> Any idea how to clean up this variable here: github.com/monero-project/monero/bl…616140bb7267b16ba7b1/src/common/dns\_utils.cpp#L330 We basically create a class `scoped_ptr` and just use that in that variable. two points to keep in mind: 1) none of the smart pointer libraries have something like `&` that we use there. 2. After getting rid of scoped\_<clipped message>

<0​xfffc:matrix.org> ptr, gcc's \_\_attribute\_\_((cleanup(freefunc))) would be perfect use there. But MSVC support is blocking us from using that.

What do you mean by "clean up" ?

<0​xfffc:matrix.org> Whoops, sorry for many messages. Didn't know that matrix relay does resent a whole message to IRC when editing a message in Matrix.

<0​xfffc:matrix.org> We defining a class and using it only once. and never touch it. And even that doesn't look like a correct design to me. monero-project/monero #8732

<0​xfffc:matrix.org> `ub_result_ptr` is `typedef class scoped_ptr<ub_result,ub_resolve_free> ub_result_ptr;`

Well, you could use the usual auto_scope_leave_caller, but if it's working and not buggy and not bad... it's just "rewrite it to what I like better", which is typically bad because someone else will come later and rewrite it to what they like better.

But here since it gets rid of a dozen lines, the change may be worth it.

<0​xfffc:matrix.org> And event `scoped_ptr` never used anywhere else.

<0​xfffc:matrix.org> Thanks, not even *only lines* it gets rid of a *generic* class that we define and never use anywhere else.

Couple dozen. Yeah, worth it I ugess.

<0​xfffc:matrix.org> `auto_scope_leave_caller ` is what I was looking for. thanks.

<d​olores.sabaneta:matrix.org> Sorry for being follower number 666 on mastodon hyc.

lol