07:07:26 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. ? 07:10:14 Possibly. IIRC this is what Aeon did. 07:10:34 It's really a case of "try it and see how it works 100 years down the line". 07:11:33 was not aware of the Aeon doing it, will check it. 07:12:55 it's an economical dilemma, from programming point of view it's an easy task if I'm correct ? 07:13:50 Yes. 07:42:13 > and we wouldn't have to worry about price not following energy cost etc. ? 07:42:14 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. 07:42:18 (/offtopic) 10:29:28 <0​xfffc:matrix.org> Any idea how to clean up this variable here: https://github.com/monero-project/monero/blob/9489586add5116a48039616140bb7267b16ba7b1/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 10:29:28 <0​xfffc:matrix.org> r, gcc's __attribute__((cleanup(freefunc))) would be perfect use there. But MSVC support is blocking us from using that. 10:30:00 <0​xfffc:matrix.org> Any idea how to clean up this variable here: https://github.com/monero-project/monero/blob/9489586add5116a48039616140bb7267b16ba7b1/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\_ 10:30:00 <0​xfffc:matrix.org> ptr, gcc's _ _attribute_ _((cleanup(freefunc))) would be perfect use there. But MSVC support is blocking us from using that. 10:30:19 <0​xfffc:matrix.org> Any idea how to clean up this variable here: https://github.com/monero-project/monero/blob/9489586add5116a48039616140bb7267b16ba7b1/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\_ 10:30:20 <0​xfffc:matrix.org> ptr, gcc's \_\_attribute\_\_((cleanup(freefunc))) would be perfect use there. But MSVC support is blocking us from using that. 10:33:26 What do you mean by "clean up" ? 10:34:34 <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. 10:35:11 <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. https://github.com/monero-project/monero/issues/8732 10:36:19 <0​xfffc:matrix.org> `ub_result_ptr` is `typedef class scoped_ptr ub_result_ptr;` 10:37:02 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. 10:37:22 But here since it gets rid of a dozen lines, the change may be worth it. 10:37:28 <0​xfffc:matrix.org> And event `scoped_ptr` never used anywhere else. 10:38:08 <0​xfffc:matrix.org> Thanks, not even *only lines* it gets rid of a *generic* class that we define and never use anywhere else. 10:38:22 Couple dozen. Yeah, worth it I ugess. 10:44:49 <0​xfffc:matrix.org> `auto_scope_leave_caller ` is what I was looking for. thanks. 12:21:13 Sorry for being follower number 666 on mastodon hyc. 19:47:30 lol