order checking for connective ops is a pain to work with

[tomara-x]

• don't check (not an option, time-bomb-style crashes are a no go)
• find a different way to avoid cycles? (hard)
• live with it? (not ideal)

142

[tomara-x]

can we "fix" the order after a connection (like what connect does), but propagate it through the whole graph? (while keeping the checking)

[this feels like substituting one recursive problem with another recursive problem]

shake was horrible, i'm not bringing back something like that!

[tomara-x]

horror itself

https://github.com/tomara-x/quartz/assets/86204514/ab748654-61c5-4a19-9061-e52aba850952

[tomara-x]

i mean, you can always make it harder >:) just remove the auto increment from connect. not subtle, but an effective way to remind you that order matters :p

[tomara-x]

increment all orders? (> 0 only)

-- sleepy amy, last week

[tomara-x]

there! 800f39c, now to figure out how to fix it better