Dr. Maxim Orlovsky
Dr. Maxim Orlovsky
With the release v0.12 these breaking changes to v0.11 are not anymore required. All important things were cherry-picked from here to v0.12.
I agree on avoiding panics overall, but here It seems panic is necessary since it reveals a business-logic bug in validation code: the index of operations seems to be inconsistent....
@zoedberg what are the specific requirements to create an UDA invoice via the `cli`?
The last three commits in https://github.com/RGB-WG/rgb/pull/248 are now do the NFT (and all other forms) of invoicing, closing this issue. I first tried to do it as a dedicated PR,...
> My proposal is to make all dependencies have std and alloc features, make them exclusive and to expose everything in both std and alloc version Yes, I do agree
> I'm adding/fixing the std and alloc features in an exclusive way I just understood that this is a breaking change - the crates downstream may stop from compiling with...
I am not talking about completing this. I am talking about fixing compilation of hundreds of crates depending on this one :)
I have no answer. I need to invest hours into checking all options against downstream crates and find the least non-inteusive
Rust-amplify is used not just by RGB. We have to fix all of the crates. This change also should go as a new 5.0 release - and there are a...
> but most of those crates are archived/abandoned Even a single non-abandoned dependency from outside of our crates is already enough not to introduce breaking changes and strictly follow semantic...