This is a small cleanup since the return value of WalletFrame methods are not used. This is in line with the usual async slot declaration.
gui: Drop unused return values in WalletFrame #15464
pull promag wants to merge 1 commits into bitcoin:master from promag:2019-02-walletframe changing 2 files +10 −20-
promag commented at 4:29 PM on February 22, 2019: member
-
gui: Drop unused return values in WalletFrame 28c86de3b1
- MarcoFalke added the label Refactoring on Feb 22, 2019
-
laanwj commented at 5:27 PM on February 22, 2019: member
The first question that comes to mind for me is: should these return values be used?
-
promag commented at 5:38 PM on February 22, 2019: member
Not currently, and if there's a need then it should be used and tagged not discarded.
-
laanwj commented at 5:45 PM on February 22, 2019: member
So the intent is to ignore errors in these functions at the moment?
-
promag commented at 6:03 PM on February 22, 2019: member
What errors?
-
jonasschnelli commented at 7:30 PM on February 22, 2019: contributor
I guess what @laanwj meant was if we should silently ignore things like if the wallet is already loaded or if we should transport that "error" to the user... I guess its captured earlier so I'm fine with this change.
-
practicalswift commented at 7:31 PM on February 22, 2019: contributor
utACK 28c86de3b11ec16ba370f07327cf5a5de0e75c99
-
promag commented at 7:58 PM on February 22, 2019: member
@jonasschnelli Yap, WalletController should validate those things, at this point these methods should simply work. I also plan to reduce those conditions so it's easier to reason about how these widgets work.
- fanquake added the label GUI on Feb 23, 2019
-
jonasschnelli commented at 5:57 AM on February 23, 2019: contributor
utACK 28c86de3b11ec16ba370f07327cf5a5de0e75c99 (post 0.18 branch-off)
- MarcoFalke added this to the milestone 0.19.0 on Feb 23, 2019
-
DrahtBot commented at 7:06 PM on February 27, 2019: member
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--174a7506f384e20aa4161008e828411d-->
Conflicts
No conflicts as of last run.
-
practicalswift commented at 7:47 PM on March 3, 2019: contributor
re-utACK 28c86de3b11ec16ba370f07327cf5a5de0e75c99
- MarcoFalke assigned jonasschnelli on Mar 3, 2019
- jonasschnelli merged this on Mar 7, 2019
- jonasschnelli closed this on Mar 7, 2019
- jonasschnelli referenced this in commit d211edb349 on Mar 7, 2019
- promag deleted the branch on Mar 7, 2019
- jasonbcox referenced this in commit e6ac31ddc7 on Nov 11, 2020
- PastaPastaPasta referenced this in commit cc14da02b4 on Sep 11, 2021
- DrahtBot locked this on Dec 16, 2021