Edit time immutability - Revision history

Apm: /* Exploring a codebase multiverse (via ALDs) */ added note on eventual dumping

2025-09-28T18:57:55Z

Exploring a codebase multiverse (via ALDs): added note on eventual dumping

← Older revision		Revision as of 20:57, 28 September 2025
Line 42:		Line 42:
	Or for educative purposes. <br>		Or for educative purposes. <br>
	{{wikitodo\|Discuss this further.}}		{{wikitodo\|Discuss this further.}}

			Code edits and resulting actual code executions <br>
			in the case of the code edits not actually committed to the codebase <br>
			will need to be dumped sooner rather than than later in order to not run out of memory.

	== Related ==		== Related ==

Apm: /* Exploring a codebase multiverse (via ALDs) */

2025-09-28T18:54:12Z

Exploring a codebase multiverse (via ALDs)

← Older revision		Revision as of 20:54, 28 September 2025
Line 37:		Line 37:
	Editing in [[annotated lambda diagrams]] actually internally does not mutate the code-AST/ADT-database. <br>		Editing in [[annotated lambda diagrams]] actually internally does not mutate the code-AST/ADT-database. <br>
	So when changing an input field manually then what actually happens is <br>		So when changing an input field manually then what actually happens is <br>
	that one sees a different part of the codebase multiverse. <br>		that one sees a different part of the codebase multiverse (of possible execution program flows). <br>
	This is visually indistinguishable from an actual mutation. <br>		This is visually indistinguishable from an actual mutation. <br>
	One might want to do that for using it as undo history graph (not list or tree). <br>		One might want to do that for using it as undo history graph (not list or tree). <br>

Apm: /* Code projection to various structural editors - code diffing */

2025-09-28T18:51:17Z

Code projection to various structural editors - code diffing

← Older revision		Revision as of 20:51, 28 September 2025
Line 25:		Line 25:
	As for challenges: <br>		As for challenges: <br>
	For one thing they need to migrate [[schema changes]] across branches that evolved in different ways. <br>		For one thing they need to migrate [[schema changes]] across branches that evolved in different ways. <br>
	Edit time immutability on top of an immutable ([[per function hash addressed]]) code database can ~~hugely~~ help with that. <br>		Edit time immutability on top of an immutable ([[per function hash addressed]]) code database can help with that. <br>

	Structural changes of the ADTs in the AST database caused by manual editing become immutably anchored in the AST database <br>		Structural changes of the ADTs in the AST database caused by manual editing become immutably anchored in the AST database <br>

Apm: /* Code projection to various structural editors - code diffing */

2025-09-28T18:50:50Z

Code projection to various structural editors - code diffing

← Older revision		Revision as of 20:50, 28 September 2025
Line 24:		Line 24:

	As for challenges: <br>		As for challenges: <br>
	For one thing they ~~needing~~ to migrate [[schema changes]] across branches that evolved in different ways. <br>		For one thing they need to migrate [[schema changes]] across branches that evolved in different ways. <br>
	Edit time immutability on top of an immutable ([[per function hash addressed]]) code database can hugely help with that. <br>		Edit time immutability on top of an immutable ([[per function hash addressed]]) code database can hugely help with that. <br>

Apm: added Category:Programming

2024-12-27T18:14:52Z

added Category:Programming

← Older revision		Revision as of 20:14, 27 December 2024
Line 59:		Line 59:

	* [https://alarmingdevelopment.org/?p=1570] Syncing schema changes across branches would hugely benefit from edit time immutability		* [https://alarmingdevelopment.org/?p=1570] Syncing schema changes across branches would hugely benefit from edit time immutability

			[[Category:Programming]]

Apm: minor additions

2024-12-27T08:20:32Z

minor additions

← Older revision		Revision as of 10:20, 27 December 2024
Line 7:		Line 7:
	(Entropically one can write on a known state not forcing kT energy dissipation not limiting one to the Landau limit, but that's not the focus here.)		(Entropically one can write on a known state not forcing kT energy dissipation not limiting one to the Landau limit, but that's not the focus here.)

	Edit time immutable means e.g. that keyboard input say into an UI input box does (in memory) not overwrite what was in there		Edit time immutable means e.g. that keyboard input, say into an UI input box, <br>
	before but rather adds a next version. ~~And the~~ UI in default mode always displays this newest version.		does (in memory) not overwrite what was in there before but rather adds a next version. <br>
			The UI in default mode always displays this newest version, but leaves the older version accessibly. <br>
			Edit histories DAG (directed acyclic graph). Plural on purpose as one can branch off of a past state and merge back.

	== What is the point of edit time immutability? ==		== What is the point of edit time immutability? ==

Line 23:		Line 25:
	As for challenges: <br>		As for challenges: <br>
	For one thing they needing to migrate [[schema changes]] across branches that evolved in different ways. <br>		For one thing they needing to migrate [[schema changes]] across branches that evolved in different ways. <br>
	Edit time immutability on top of an immutable ([[per function hash addressed]]) code database can hugely ~~helps~~ with that. <br>		Edit time immutability on top of an immutable ([[per function hash addressed]]) code database can hugely help with that. <br>

	Structural changes of the ADTs in the AST database caused by manual editing become immutably anchored in the AST database <br>		Structural changes of the ADTs in the AST database caused by manual editing become immutably anchored in the AST database <br>
Line 29:		Line 31:
	structural (ADT) changes can be traced backwards to the common branch-points, and from there forward again to the alternate branch. <br>		structural (ADT) changes can be traced backwards to the common branch-points, and from there forward again to the alternate branch. <br>
	A nearest common ancestor in schema can be synthesized beforehand. <br>		A nearest common ancestor in schema can be synthesized beforehand. <br>
	A minimal smart diff of natural representation that is a bit more discovered than invented. <br>		A minimal smart diff of natural representation that seems a bit more discovered than invented. <br>

	=== Exploring a codebase multiverse (via ALDs) ===		=== Exploring a codebase multiverse (via ALDs) ===

Apm: /* Related / added links Annotated lambda diagrams * Annotated lambda diagram mockups

2024-12-27T08:04:39Z

Related: added links * Annotated lambda diagrams * Annotated lambda diagram mockups

← Older revision		Revision as of 10:04, 27 December 2024
Line 48:		Line 48:
	* [[Structural editing]]		* [[Structural editing]]
	* [[Projectional editing]]		* [[Projectional editing]]
			----
			* [[Annotated lambda diagrams]]
			* [[Annotated lambda diagram mockups]]
	----		----
	* [[node editor]]s		* [[node editor]]s

Apm: /* Related */

2024-09-03T08:43:57Z

← Older revision		Revision as of 10:43, 3 September 2024
Line 45:		Line 45:
	* [[AST ADT chicken egg problem]]		* [[AST ADT chicken egg problem]]
	* [[Wild future of coding ideas]]		* [[Wild future of coding ideas]]
			----
			* [[Structural editing]]
			* [[Projectional editing]]
	----		----
	* [[node editor]]s		* [[node editor]]s

Apm: /* External links */

2024-09-03T07:16:32Z

External links

← Older revision		Revision as of 09:16, 3 September 2024
Line 51:		Line 51:
	== External links ==		== External links ==

	* [https://alarmingdevelopment.org/?p=1570] Syncing schema changes across branches would hugely benefit from ~~edir~~ time immutability		* [https://alarmingdevelopment.org/?p=1570] Syncing schema changes across branches would hugely benefit from edit time immutability

Apm: added link to relevant blogpost about syncing schema changes

2024-09-03T07:14:47Z

added link to relevant blogpost about syncing schema changes

← Older revision		Revision as of 09:14, 3 September 2024
Line 48:		Line 48:
	----		----
	* [[node editor]]s		* [[node editor]]s

			== External links ==

			* [https://alarmingdevelopment.org/?p=1570] Syncing schema changes across branches would hugely benefit from edir time immutability

Edit time immutability - Revision history

Apm: /* Exploring a codebase multiverse (via ALDs) */ added note on eventual dumping

Apm: /* Exploring a codebase multiverse (via ALDs) */

Apm: /* Code projection to various structural editors - code diffing */

Apm: /* Code projection to various structural editors - code diffing */

Apm: added Category:Programming

Apm: minor additions

Apm: /* Related */ added links * Annotated lambda diagrams * Annotated lambda diagram mockups

Apm: /* Related */

Apm: /* External links */

Apm: added link to relevant blogpost about syncing schema changes

Apm: /* Related / added links Annotated lambda diagrams * Annotated lambda diagram mockups