-
(hidden) lNPIawEyA [[(hidden) SU8hr25lN]]
-
was thinking re: [[advanced refactoring / abstraction]] - using similar utilities like [[codemods]] (or, rather, working with the #[[(hidden) -g8qO2BEP]]), to have a "magic wand" in your editor, which allows you to extract some local variables of a function (however deep in the call stack) into that function's arguments, or into a function that's higher (before) in the call stack (abstraction). what's hard is the [[(hidden) Vtxi7b35b]] -
-
from the [[(hidden) qF79KNVBl]].each (?) @ [[(hidden) S-ygYfi0j]], you can start extracting however many variables you want. it's not even "statements vs data" (you're "supposed" to extract only the data, & of course not all of it) - even statements can be extracted. here comes the #observation -- technically, you can extract literally everything. and, well, say we have a function to describe the whole world (at some point of time, probably?) - if we figure out the function itself, than by abstracting [[(hidden) kc2jYpsn6]] aren't we? :kek: re: extracting statements - is the abstraction still any useful then? i think yes.
-
-
(hidden) aUPKW-8vZ
-
-
(hidden) myvPDLLfs
-
(hidden) o5fR1I8N8
-
(hidden) pEfR4h-6l
-
[[git-stacked-rebase]]
-
{{[[TODO]]}} need a "what to be aware of" / "patterns to avoid with this workflow" info @ the readme.
-
{{[[TODO]]}} boolean table for options compatibility?
-
{{[[TODO]]}} `diff`ing commands built-in? because i use my own git aliases but these specific ones are often useful when using this pattern of stacked diffs
-
-
(hidden) Dhx1JQizK
-
(hidden) Nv8PMFRMW #observation [[(hidden) C2gsuHThd]]
-
(hidden) AVcM5iyET
-
(hidden) igtJr0Aov #[[(hidden) S-ygYfi0j]]
-
(hidden) YZcrP5XRE
-
[[git-stacked-rebase]]
-
{{[[TODO]]}} shortening some namings would make sense because they're too verbose now i think & since we've went thru quite a few different scenarios on where they're used, i think
-
{{[[TODO]]}} i think it makes sense to get rid of the "--arg won't work if --sub-arg is not specified" notion (--push without --force, --branch-sequencer without --exec)
-
i initially thought that it's always good to remember that you're e.g. force pushing. but i now think that it's different, because of the context. you use this tool, git-stacked-rebase, to specifically work with stacked diffs (branches), and you (should) automatically expect & be aware that 1. it overwrites history, 2. you can screw yourself up a bit if you don't know what you're doing (though, since commits already exist, it'd be more of a time-consuming activity to recover them via reflog or to recover the branches to correct state or similar, if you messed up, but it's not like a permanent lost of progress).
-
in short, a knife is a useful tool. if you screw up you can hurt yourself. you cannot have good tools if you're afraid that someone not yet ready to use the tool will screw up that you oversimplify / "fool-proof" the tool so much it become useless. maybe better example would be nuclear power idk anyhow we're getting rid of the bs and making it good
-
-
-
(hidden) XtgC0gcVa
-
{{[[TODO]]}} (hidden) ldulDbii7
-
(hidden) fRFBDqMw9
-
(hidden) PK_bQZG2_
-
(hidden) Ed0anZxsk
-
(hidden) N_6cqI0vu #[[(hidden) WNCAo37xy]]
-
(hidden) lSecmrpE8
-
(hidden) T345Tmw3A