unison/unison-src/transcripts/cycle-update-1.output.md

Update a member of a cycle, but retain the cycle.

``` unison
ping : 'Nat
ping _ = !pong + 1

pong : 'Nat
pong _ = !ping + 2
```

``` ucm

  Loading changes detected in scratch.u.

  I found and typechecked these definitions in scratch.u. If you
  do an `add` or `update`, here's how your codebase would
  change:
  
    ⍟ These new definitions are ok to `add`:
    
      ping : 'Nat
      pong : 'Nat

```
``` ucm
scratch/main> add

  ⍟ I've added these definitions:
  
    ping : 'Nat
    pong : 'Nat

```
``` unison
ping : 'Nat
ping _ = !pong + 3
```

``` ucm

  Loading changes detected in scratch.u.

  I found and typechecked these definitions in scratch.u. If you
  do an `add` or `update`, here's how your codebase would
  change:
  
    ⍟ These names already exist. You can `update` them to your
      new definition:
    
      ping : 'Nat

```
``` ucm
scratch/main> update

  Okay, I'm searching the branch for code that needs to be
  updated...

  That's done. Now I'm making sure everything typechecks...

  Everything typechecks, so I'm saving the results...

  Done.

scratch/main> view ping pong

  ping : 'Nat
  ping _ =
    use Nat +
    pong() + 3
  
  pong : 'Nat
  pong _ =
    use Nat +
    ping() + 2

```
break cycle-update.md into 4 smaller transcripts 2022-09-21 20:32:59 +03:00			`Update a member of a cycle, but retain the cycle.`

Update the transcripts with `cmark` `cmark`’s pretty-printer matches our output pretty well, with a few differences: - it puts a space between the fence and the info string for in code blocks; - it prefers `-` over `` for bulleted lists (as do I) and it indents them; - it `\`-escapes certain chars very conservatively; - it prefers indented/unfenced code blocks if there is no info string; and - it prefers `` over `_` (unlike any sane person). This also shows how the change fixes a number of issues: - fix2158-1.output.md also illustrates how this change fixes #1809; - alias-many.output.md and input-parse-errors.output.md show how fenced code blocks without an info string would use the beginning of the content as the info string; - transcripts-round-trip/main.output.md shows how output blocks for generated `unison` stanzas (which could contain nested fenced blocks) might not have long-enough fences; and - error-messages.output.md and generic-parse-errors.output.md show how Unison errors were reported on the wrong line number (and thus the printed error lines were also incorrect). 2024-07-10 17:46:18 +03:00			``` unison
break cycle-update.md into 4 smaller transcripts 2022-09-21 20:32:59 +03:00			`ping : 'Nat`
			`ping _ = !pong + 1`

			`pong : 'Nat`
			`pong _ = !ping + 2`
			```

Add a space before code block info strings This is for consistency with the `cmark` style. Now the blocks we still pretty-print ourselves will match the bulk of them that `cmark` produces. 2024-07-10 19:17:15 +03:00			``` ucm
break cycle-update.md into 4 smaller transcripts 2022-09-21 20:32:59 +03:00
Adding a message for when ucm started reloading changes 2023-12-22 14:55:24 +03:00			`Loading changes detected in scratch.u.`

break cycle-update.md into 4 smaller transcripts 2022-09-21 20:32:59 +03:00			`I found and typechecked these definitions in scratch.u. If you`
			do an `add` or `update`, here's how your codebase would
			`change:`

			⍟ These new definitions are ok to `add`:

			`ping : 'Nat`
			`pong : 'Nat`

			```
Add a space before code block info strings This is for consistency with the `cmark` style. Now the blocks we still pretty-print ourselves will match the bulk of them that `cmark` produces. 2024-07-10 19:17:15 +03:00			``` ucm
Replace '.' references with scratch/main 2024-06-12 01:22:09 +03:00			`scratch/main> add`
break cycle-update.md into 4 smaller transcripts 2022-09-21 20:32:59 +03:00
			`⍟ I've added these definitions:`

			`ping : 'Nat`
			`pong : 'Nat`

			```
Update the transcripts with `cmark` `cmark`’s pretty-printer matches our output pretty well, with a few differences: - it puts a space between the fence and the info string for in code blocks; - it prefers `-` over `` for bulleted lists (as do I) and it indents them; - it `\`-escapes certain chars very conservatively; - it prefers indented/unfenced code blocks if there is no info string; and - it prefers `` over `_` (unlike any sane person). This also shows how the change fixes a number of issues: - fix2158-1.output.md also illustrates how this change fixes #1809; - alias-many.output.md and input-parse-errors.output.md show how fenced code blocks without an info string would use the beginning of the content as the info string; - transcripts-round-trip/main.output.md shows how output blocks for generated `unison` stanzas (which could contain nested fenced blocks) might not have long-enough fences; and - error-messages.output.md and generic-parse-errors.output.md show how Unison errors were reported on the wrong line number (and thus the printed error lines were also incorrect). 2024-07-10 17:46:18 +03:00			``` unison
break cycle-update.md into 4 smaller transcripts 2022-09-21 20:32:59 +03:00			`ping : 'Nat`
			`ping _ = !pong + 3`
			```

Add a space before code block info strings This is for consistency with the `cmark` style. Now the blocks we still pretty-print ourselves will match the bulk of them that `cmark` produces. 2024-07-10 19:17:15 +03:00			``` ucm
break cycle-update.md into 4 smaller transcripts 2022-09-21 20:32:59 +03:00
Adding a message for when ucm started reloading changes 2023-12-22 14:55:24 +03:00			`Loading changes detected in scratch.u.`

break cycle-update.md into 4 smaller transcripts 2022-09-21 20:32:59 +03:00			`I found and typechecked these definitions in scratch.u. If you`
			do an `add` or `update`, here's how your codebase would
			`change:`

			⍟ These names already exist. You can `update` them to your
			`new definition:`

			`ping : 'Nat`

			```
Add a space before code block info strings This is for consistency with the `cmark` style. Now the blocks we still pretty-print ourselves will match the bulk of them that `cmark` produces. 2024-07-10 19:17:15 +03:00			``` ucm
Replace '.' references with scratch/main 2024-06-12 01:22:09 +03:00			`scratch/main> update`
break cycle-update.md into 4 smaller transcripts 2022-09-21 20:32:59 +03:00
print better update info messages 2023-11-14 06:36:03 +03:00			`Okay, I'm searching the branch for code that needs to be`
			`updated...`

			`That's done. Now I'm making sure everything typechecks...`

			`Everything typechecks, so I'm saving the results...`
fix transcripts 2023-11-08 19:54:50 +03:00
			`Done.`
break cycle-update.md into 4 smaller transcripts 2022-09-21 20:32:59 +03:00
Replace '.' references with scratch/main 2024-06-12 01:22:09 +03:00			`scratch/main> view ping pong`
break cycle-update.md into 4 smaller transcripts 2022-09-21 20:32:59 +03:00
			`ping : 'Nat`
			`ping _ =`
			`use Nat +`
Switch to `foo()` with no space as preferred syntax instead of `!foo` 2024-06-21 00:52:57 +03:00			`pong() + 3`
break cycle-update.md into 4 smaller transcripts 2022-09-21 20:32:59 +03:00
			`pong : 'Nat`
			`pong _ =`
			`use Nat +`
Switch to `foo()` with no space as preferred syntax instead of `!foo` 2024-06-21 00:52:57 +03:00			`ping() + 2`
break cycle-update.md into 4 smaller transcripts 2022-09-21 20:32:59 +03:00
			```