Kristoffer Dalby cef5338cfe types/change: panic on Merge with conflicting TargetNode values ... Merging two changes targeted at different nodes is not supported because the result can only carry one TargetNode. The second target's content would be silently misrouted. Add a panic guard that catches this at the Merge call site rather than allowing silent data loss. In production, Merge is only called with broadcast changes (TargetNode=0) so the guard acts as insurance against future misuse.		2026-04-10 13:18:56 +01:00
..
change.go	types/change: panic on Merge with conflicting TargetNode values	2026-04-10 13:18:56 +01:00
change_test.go	all: upgrade to Go 1.26rc2 and modernize codebase	2026-02-08 12:35:23 +01:00