Brice
We should also ensure that the unexpected behavior from https://github.com/stacks-network/stacks-blockchain/issues/2696 is unaffected by this change.
The same problem happens if I change the network `?chain=testnet`, which correctly shows localhost:3999 in the UI:
Yes, it looks like it still is an issue.
You can use this contract on testnet for a simple reproducer: ST1SJ3DTE5DN7X54YDH5D64R3BCB6A2AG2ZQ8YPD5.nearby-magenta-termite
@LunarPunks can you post a screenshot? I'm not seeing post-condition options on the Syvita sandbox.
Changes to the behavior with this implementation (I will be appending to this list): * A value of type `trait_A` may be passed as type `trait_B`, provided that `trait_B` is...
Issues #3214 and #3215 should be resolved here also.
Echoing my Discord comments here for record: The code handling `pow` looks like this, which explains those cases: ```rust if base == 0 && power == 0 { // Note...
The unit test `chainstate::stacks::db::transactions::test::test_checkerrors_at_runtime` is expected to fail with this change, because what used to trigger a runtime check error is now legal: ```clarity (use-trait trait .foo.foo) (define-data-var mutex bool...
> If my reading is correct, in its current state, the proposed implementation (centered around the idea of introducing a new type for traits) would not be backward compatible. By...