--- Log opened Tue Mar 18 00:00:53 2025
01:31 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #secp256k1
01:33 -!- ghost43_ [~ghost43@gateway/tor-sasl/ghost43] has quit [Ping timeout: 264 seconds]
05:24 < bitcoin-git> [secp256k1] muxator opened pull request #1665: build: add back configure.ac change that was left out when integrating v0.3.0 (master...configure.ac-missed-in-0.3.0) https://github.com/bitcoin-core/secp256k1/pull/1665
05:25 < bitcoin-git> [secp256k1] muxator closed pull request #1665: build: add back configure.ac change that was left out when integrating v0.3.0 (master...configure.ac-missed-in-0.3.0) https://github.com/bitcoin-core/secp256k1/pull/1665
06:43 < josie> thanks all for the links. sipa - what does a "hard break" mean in this context? 
07:21 < sipa> josie: compilation will fail for everyone
07:21 < sipa> compare the current int function(uint8_t* seckey32);
07:22 < sipa> with a hypothetical int function(uint8_t (*seckey32)[32]);
07:23 < sipa> if you have a variable uint8_t keydata[32]; declared, then the first you call as function(keydata);, while the second you call as function(&keydata);
07:23 < sipa> so we can't just change the calling convention without breaking all users
07:32 < bitcoin-git> [secp256k1] muxator opened pull request #1666: frost: use constant instead of allocating a variable on the stack (master...frost-use-constants) https://github.com/bitcoin-core/secp256k1/pull/1666
07:33 < bitcoin-git> [secp256k1] muxator closed pull request #1666: frost: use constant instead of allocating a variable on the stack (master...frost-use-constants) https://github.com/bitcoin-core/secp256k1/pull/1666
09:20 < josie> sipa: got it, i misunderstood your last sentence as saying adding a *new API* with this convention would be a hard break. but rather, you're saying we would need to decided now whether or not to have the new API follow this convention (which would break convention with the existing APIs), otherwise we would need to hard break the new API in the future if we decided to move to the new convention
11:31 < bitcoin-git> [secp256k1] muxator opened pull request #1667: frost: remove redundant secp256k1_gej_mul_scalar() when the first factor is infinity (master...frost-remove-redundant-mul-scalar) https://github.com/bitcoin-core/secp256k1/pull/1667
11:31 < bitcoin-git> [secp256k1] muxator closed pull request #1667: frost: remove redundant secp256k1_gej_mul_scalar() when the first factor is infinity (master...frost-remove-redundant-mul-scalar) https://github.com/bitcoin-core/secp256k1/pull/1667
15:28 -!- tromp [~textual@2a02:a210:cba:8500:2c80:dbc6:3e9d:a12d] has quit [Ping timeout: 265 seconds]
18:35 -!- jonatack [~jonatack@user/jonatack] has joined #secp256k1
18:37 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 246 seconds]
--- Log closed Wed Mar 19 00:00:56 2025