Forward-port check-semver scripts and seal WorkExt - #6548
Conversation
45a1b1e to
802005f
Compare
|
🚨 API BREAKING CHANGE DETECTED To see the changes click details on "Continuous integration / Check (api)" job then expand "Run api" and scroll to the end of the section. |
802005f to
d20634a
Compare
|
🚨 API BREAKING CHANGE DETECTED To see the changes click details on "Continuous integration / Check (api)" job then expand "Run api" and scroll to the end of the section. |
d20634a to
a1b05dc
Compare
a1b05dc to
dff185b
Compare
|
🚨 API BREAKING CHANGE DETECTED To see the changes click details on "Continuous integration / Check (api)" job then expand "Run api" and scroll to the end of the section. |
|
🚨 API BREAKING CHANGE DETECTED To see the changes click details on "Continuous integration / Check (api)" job then expand "Run api" and scroll to the end of the section. |
|
bf7e391: up to date forward port of the new script, and added a commit for the higher shellcheck standards here on master. |
An un-sealed WorkExt exposes a non-additive feature. With the `std` feature is enabled, a function is added without a default implementation. Sealing the trait since it is not designed for consumers to implement. This also makes it additive.
bf7e391 to
2f420f8
Compare
|
🚨 API BREAKING CHANGE DETECTED To see the changes click details on "Continuous integration / Check (api)" job then expand "Run api" and scroll to the end of the section. |
|
2f420f8: rebase for API file fixes |
|
I'll ack. It reads a bit weirdly to me to use |
|
I didn't read the shell all that closely since its a port. |
I can fix this up. I ain't the greatest shell hacker. |
Clean up a lot of the handling by leveraging check-semver features. This allows the script to handle the semver trick.
2f420f8 to
2be8875
Compare
|
🚨 API BREAKING CHANGE DETECTED To see the changes click details on "Continuous integration / Check (api)" job then expand "Run api" and scroll to the end of the section. |
|
2be8875: re-order main function, also fix the bash array initialization |
|
hehe you put the main function at the bottom, it goes at the top ya goose :) If you want, take a look at |
That is awesome. I don't have strong feelings on it, but it does seem like the "where does the main function live" convention isn't very strong? Been trying to read up on general best shell practices and it seems all over the place. |
|
Obviously my subjective opinion is the most correct and I rekon important stuff goes at the top of the file. 'Helpers' and less import stuff below. Andrew is pleasantly ambivalent on such triviality so in rust-bitcoin I get to push most of these ideas through ... |
Forward-port of #6536, with some shell style cleanup.