--- Log opened Mon Apr 10 00:00:28 2023 02:00 -!- wilfredallyn[m] [~wilfredal@2001:470:69fc:105::3:2b22] has quit [Quit: You have been kicked for being idle] 03:10 < darosior> It would be great to have a new release of rust-miniscript, there hasn't been one in 6 months and i'm piling up rebased patches on my fork for Liana. (For instance for multipath descriptors support.) 07:45 < andytoshi> for sure 07:45 < andytoshi> i'm not sure what sanket1729 schedule looks like but i'd like to try to push on that this week (there's just a big mess of crates we've also gotta update for bitcoin 0.30..) 08:07 < stevenroose> I mentioned this somewhere in a comment, but some of our dependent crates (like miniscript) could try start using range versions for the rust-bitcoin dep. Especially if few functioonality is used, it might work most times. But we need an easy way to then start adding the different version to the CI matric. 08:13 < andytoshi> that's a neat idea. i'm doubtful for rust-miniscript 08:13 < andytoshi> what i'd really like is for us to split out bitcoin-primitives which hopefully won't change so much.. 14:00 < stevenroose> Request for input :) For core-rpc do we want to allow users to enter unchecked addresses or refuse that? 14:00 < stevenroose> How it's currently released, that's not allowed 14:10 < andytoshi> what does it mean to "enter an unchecked address" 14:10 < andytoshi> checking vs not checking is a type-level thing 14:10 < andytoshi> not something that is visible in the serialization 14:21 < stevenroose> I'm talking about using it as a functioon argument of an API method.. 14:22 < stevenroose> Basically the difference between taking &Address vs taking &Address 20:28 -!- BlueMatt_ [~BlueMatt@ircb.bluematt.me] has quit [Quit: Quit] 20:28 -!- BlueMatt [~BlueMatt@ircb.bluematt.me] has joined #bitcoin-rust 20:39 -!- BlueMatt [~BlueMatt@ircb.bluematt.me] has quit [Quit: Quit] 20:40 -!- BlueMatt [~BlueMatt@ircb.bluematt.me] has joined #bitcoin-rust --- Log closed Tue Apr 11 00:00:29 2023